Hi,

I just upgraded our local school's network, and users are complaining about Firefox crashing all the time. Indeed, it looks like 52.0.2 is much more crash-prone than its predecessor 45.x.

What now?

I use Firefox 52.02 in slackware-current and all is ok,no crash

To make things clear: is it Firefox 52.0.2 ESR from Slackware 14.2? From your comment about its preceding version I'm guessing that it is.

1 members found this post helpful.

Its not crashing for me in Current and I use it all the time. Perhaps an add-on/plugin is affecting it (looks over at Shockwave Flash). I use lightbeam, openh264, ant video, and Firefox hasn't crashed on me once.

Firefox 52.0.2 ESR (Patrick's official build) is very stable here on Slackware 14.2 64 bit.

Did you see this thread?

http://www.linuxquestions.org/questi...up-4175603501/

Perhaps it is the same issue?

1 members found this post helpful.

firefox 52.x has Electrolysis enabled by default, which is a huge improvement, but not all the addons works fine and some even disable it, go to "about:support" in the address bar (check for "multi process") and see

https://www.arewee10syet.com/

https://wiki.mozilla.org/Electrolysis/Addons

1 members found this post helpful.

I just set up MLED 14.2 64 in vbox vm, FF ESR 52.0.2 (64-bit), hasn't crashed for me, any web sites you know it crashes on?

I'm running Slackware 14.1 32bit

mozilla-firefox-52.0.2esr-i486-2_slack14.1.txz
from
http://packages.slackware.com/?r=sla..._slack14.1.txz

crashes (even in safe-mode) when attempting to access https://www.touchsupport.com/


While https://www.touchsupport.com/about-us/ opens without any problems.

Seamonkey browser exhibits the same crash behavior on the same pages.

/var/log/packages/seamonkey-2.46-i486-3_slack14.1

Konqueror browser Version 4.10.5 opens both
https://www.touchsupport.com/about-us/ and https://www.touchsupport.com/ without any issues.

Can anyone duplicate this?
How can I troubleshoot this further?

1 members found this post helpful.

I have Slackware 14.1 32-bit installed in our local school's network. I upgraded all client desktops last weekend, and since yesterday, I get crash reports galore on all machines for Firefox.

There's clearly a problem. I strongly suggest to revert to 45 ESR until this is sorted out.

Cheers,

Niki

1 members found this post helpful.

From what I've seen on this forum regarding recent Firefox update, this combination (Slackware 14.1 and Firefox 52) seems to be problematic.

Could be a problem with new requirements that v52 introduced, like for example gstreamer flag that was noted in old 14.1 slackbuild has been deprecated.
From what I've seen gstreamer is now irrelevant, latest version needs parts of ffmpeg, specifically the libvpx part.
It's possible some sites have embedded media which cause the crash in case ffmpeg is missing or compiled without required media library.
Note that I don't use 14.1 or firefox, but I've built icecat v52 (which is based on firefox v52) on slackware64-14.2 and linked it with ffmpeg-3.2.4 libvpx-1.6.1 and gtk+2-2.24.31 with no problem, it hasn't crashed yet.
Other than that, I don't know why it would crash, could be anything, even python or automake version mismatch, it's not like it hasn't happened before.

1 members found this post helpful.

Thank you Niki is very sound advice..

However when you say-
.
Can you detect any kinda pattern or similarities in the type of errors causing the crashes?

I'm trying to approach this as a opportunity for me to learn (slowly) some basic application debugging. I am hoping there are individuals on this board that can provide me with some basic guidance on HOW TO narrow down the actual cause of the crashes.

Why is it occurring here and not here?
Meaning what is the most likely error causing slice of code (or even just general section of code) that is different on this page that is NOT on that page.

Does anyone here know WHERE the crash error logs can be found on a slackware machine?
Nothing shows up in:

Quote:

/var/log/syslog /var/log/messages /var/log/Xorg.0.log

I understand mozzilla firefox provides the about:crashes screen within the browser itself but nothing is appearing for me there. I imagine the Operating System MUST log an error someplace BEFORE it appears to the Browser API. Does anyone on this board now where I should first look for it?

By launching firefox from within the terminal window:

I am able to see:

when I attempting to access https://www.touchsupport.com/

But then the trail goes cold for me.

I understand segmentation faults CAN be caused by failing RAM chips.. So i ran memtest+ for three passes with no errors and was hoping someone else could corroborate the same crash using the same:

System 14.1 32bit
Software version from official repository mozilla-firefox-52.0.2esr-i486-2_slack14.1.txz and
Website https://www.touchsupport.com/.

"There are four common mistakes that lead to segmentation faults: dereferencing NULL, dereferencing an uninitialized pointer, dereferencing a pointer that has been freed (or deleted, in C++) or that has gone out of scope (in the case of arrays declared in functions), and writing off the end of an array. " Source:http://www.cprogramming.com/debugging/segfaults.html

It would be FUN to find where exactly this is occurring or even just to eliminate where it is NOT occurring. But my debugging knowledge is pretty slim.

Any advice for the debugging, SlowLearner?

If you want to debug it, build firefox with debugging symbols, run it in gdb, reproduce the crash, get a backtrace and finally share it with the firefox devs.

Sorry, but I don't have time to potty-train the new Firefox version. I'll see how I can get my hands on the previous 45.8.0 version (which unfortunately disappeared from all the Slackware mirrors) and install that while the Firefox devs get their act together.

Cheers,

Niki

1 members found this post helpful.