LinuxQuestions.org - Firefox - segmentation fault after DEC 16 2015

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Firefox - segmentation fault after DEC 16 2015 (https://www.linuxquestions.org/questions/slackware-14/firefox-segmentation-fault-after-dec-16-2015-a-4175561826/)

Firefox - segmentation fault after DEC 16 2015

Slackware64-current
After 16 DEC updates, my Firefox crashes with Segmentation fault, everytime when i open http://www.onet.pl
I removed flashplayer by deleting /usr/lib64/mozilla/plugin/libflashplayer.so but firefox crashes as before.
Next updates from DEC 18 not fix this.
I can't recognize is it a Mozilla or Slackware problem?

Tested with http://www.onet.pl/

no problem here.

Yes, me too, firefox is VERY crashy for me after the latest update. I've disabled all addons, and created a new profile, but the problem is still there. For me, it mostly happens closing tabs. It's repeatable. It happens with Twitter and with Google Drive.

*But* it's only happening on one of my boxes ... as a wild guess, Olek, do you have an AMD processor?

I've tried to look at the core dump; there are >70 threads, and they all look innocent, except thread 1:

Code:

Using host libthread_db library "/lib64/libthread_db.so.1".

Core was generated by `firefox'.

Program terminated with signal SIGSEGV, Segmentation fault.

#0  0x00007f2318b4f209 in raise () from /lib64/libpthread.so.0

[Current thread is 1 (Thread 0x7f22f51fe700 (LWP 7649))]

[...]

Thread 1 (Thread 0x7f22f51fe700 (LWP 7649)):

#0  0x00007f2318b4f209 in raise () at /lib64/libpthread.so.0

#1  0x00007f23135e7a7f in  () at /usr/lib64/firefox-43.0/libxul.so

#2  0x00007f2313bd5149 in  () at /usr/lib64/firefox-43.0/libxul.so

#3  0x00007f2318b4f340 in <signal handler called> () at /lib64/libpthread.so.0

#4  0x0000000000000000 in  ()

#5  0x0000000000000000 in  ()

Well there was an issue that's why Mozilla put out a new one 43.0.1 it had hot fixes I would think.
you may want to grab a repack till Pat builds another. firefox repacker. https://gist.github.com/ruario/9672798

Confirmed
Unfortunately, AMD is not to be blamed this time, I have i5-3360, system is current multilib.
Closing tab with twitter or google drive is 100% repeatable, other crashes on page switching seem to be radom.
New profile or safe mode do not help
Tried to revert back to 42.0 - the same, so I have just upgraded to 43.0.1, no success.
Here's what strace shows right after the crash caused by clausing tab with twitter:

Code:

futex(0x7f66756510cc, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f66756510c8, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1

recvmsg(4, 0x7ffef9a176f0, 0)          = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}], 5, 0) = 1 ([{fd=23, revents=POLLIN}])

read(23, "\372", 1)                    = 1

futex(0x7f66756510cc, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f66756510c8, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1

futex(0x7f6656aa1fbc, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f6656aa1fb8, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1

+++ killed by SIGSEGV +++

Segmentation fault

Quote:

Originally Posted by 55020 (Post 5466296)

*But* it's only happening on one of my boxes ... as a wild guess, Olek, do you have an AMD processor?

No, i have I3-4130.
Now i upgraded 32-bit slackware-current on ma laptop with Intel Core2 Duo. And Firefox crashes the same way.
To be precise - Firefox crashes several seconds after opening site www.onet.pl
No action is needed. You can just wait till program will crash.

Confirmed, too

onet.pl crashes every time after ten seconds:

Code:

poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=84, events=POLLIN}], 6, 0) = 0 (Timeout)

futex(0x7f526d6510cc, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f526d6510c8, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1

recvmsg(4, 0x7fff2b7605f0, 0)          = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=84, events=POLLIN}], 6, 0) = 1 ([{fd=23, revents=POLLIN}])

read(23, "\372", 1)                    = 1

recvmsg(4, 0x7fff2b7605f0, 0)          = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=84, events=POLLIN}], 6, 0) = 0 (Timeout)

futex(0x7f524ea30e5c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f524ea30e58, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1

recvmsg(4, 0x7fff2b7605f0, 0)          = -1 EAGAIN (Resource temporarily unavailable)

poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=84, events=POLLIN}], 6, 0) = 0 (Timeout)

[NPAPI 12904] ###!!! ABORT: Aborting on channel error.: file /tmp/firefox-43.0.1/ipc/glue/MessageChannel.cpp, line 1768

[NPAPI 12904] ###!!! ABORT: Aborting on channel error.: file /tmp/firefox-43.0.1/ipc/glue/MessageChannel.cpp, line 1768

+++ killed by SIGSEGV +++

Segmentation fault

Quote:

Originally Posted by tomtomjkw (Post 5466334)

Code:

[NPAPI 12904] ###!!! ABORT: Aborting on channel error.: file /tmp/firefox-43.0.1/ipc/glue/MessageChannel.cpp, line 1768

[NPAPI 12904] ###!!! ABORT: Aborting on channel error.: file /tmp/firefox-43.0.1/ipc/glue/MessageChannel.cpp, line 1768

+++ killed by SIGSEGV +++

Segmentation fault

regarding this I found this bug report, not sure if related...

you can try to check if it's gstreamer-related toggling "media.gstreamer.enabled" in about:config

Sorry, I forgot to mention: that doesn't help :(

Quote:

Originally Posted by ponce (Post 5466337)

you can try to check if it's gstreamer-related toggling "media.gstreamer.enabled" in about:config

I tried this before I wrote my first post. Disabling media.gstreamer.enabled not helping.

I was about to post something about this yesterday. I've also been having a lot of segfaults with firefox after the last update. Will need to see if upgrading to 43.0.1 will do the trick.

Might be related to javascript, when "noscript plugin" is ON, Firefox doesn't crash but as soon as I allow noscript to execute scripts (from onet.pl), Firefox crashes.

Thank you!
I've just installed noscript, left the default settings and it doesn't crash anymore.

Weird. I don't have that plugin at all. As a matter of fact, it was a clean profile and it still crashed.

NoScript is an extension (add-on).

When I fire up Firefox for the first time, I install a couple of extensions such as NoScript and uBlock origin ; I don't roam on the web without these two.

I wanted to see if Firefox were to crash on my machine but It didn't ; when I switched off NoScript, Firefox crashed, that's It.