PM 26.2.1 random crashing. Topic is solved

[BazBear]

PM has been randomly crashing an average of once per day since the 26.2.1 update. The odd part is that these crashes don't seem to be triggering an error message, nor an apport (Ubuntu's error reporting system) error report dialog box. I had suspected it might be the 4.5.1 kernel I was using, so I tried using the "official" 3.16 series kernel instead, but I'm still seeing the random crashing. I'm using Lubuntu 14.04.4 on a Acer Aspire One 722 (1 Ghz 2 core x64 AMD processor, 2 GB RAM).

EDIT - Actually, it did trigger apport, it just didn't give me a notification. From the apport log in /var/log -

Code: Select all

ERROR: apport (pid 6649) Thu Apr 21 08:33:49 2016: called for pid 2028, signal 11, core limit 0
ERROR: apport (pid 6649) Thu Apr 21 08:33:49 2016: executable: /opt/palemoon/palemoon (command line "palemoon")
ERROR: apport (pid 6649) Thu Apr 21 08:33:50 2016: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 6649) Thu Apr 21 08:33:50 2016: debug: session gdbus call: 
ERROR: apport (pid 6649) Thu Apr 21 08:33:50 2016: apport: report /var/crash/_opt_palemoon_palemoon.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS

[trava90]

I too am using the Linux 4.5 kernel and have not seen any crashing on my system. Are you able to reliably reproduce the crash?

[ipsirc]

signal 11 error is usually caused by hw problems, mostly bad memory. Run a memtest!

[BazBear]

signal 11 error is usually caused by hw problems, mostly bad memory. Run a memtest!

The memory tested fine, but thanks for the suggestion.

Oddly, this problem hasn't reoccurred since I started this thread 3 days ago. The only thing I've changed since then is installing the 4.5.2 kernel.

[BazBear]

I too am using the Linux 4.5 kernel and have not seen any crashing on my system. Are you able to reliably reproduce the crash?

No, it is... or hopefully now was (see my post above)... seemingly totally random. The only constant I can think of is that I believe I had an open tab playing a YouTube video each time the browser crashed.

All seems well right now, so if it behaves for another couple of days, I'm just gonna shrug and mark this [SOLVED].