You are not logged in.
It just happened again. I'll give aurora a try.
Managed to get something:
onreadystatechange@resource://gre/modules/XPIProvider.jsm -> jar:file:///home/claudio/.mozilla/firefox/5lbr2ct4.default/extensions/jid1-F9UJ2thwoAm5gQ@jetpack.xpi!/bootstrap.js -> resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/request.js:98
Segmentation fault (core dumped)
EDIT: Firefox Aurora crashed after less than 5 minutes. Giving ESR a shot this time...
EDIT2: A few hours after Firefor-ESR still didn't crashed. I got to get some sleep, just leaving the feedback, "tomorrow" I'll leave some more feedback if needed.
Last edited by ClaudioP (2013-12-26 07:10:06)
Ahh... stuff
Offline
After a pacman -Syu yesterday the situation is unchanged for me. Firefox 26 still crashing, Firefox ESR 24 not crashing on both my PCs, both nvidia.
Offline
There is a new build of the 331.20 driver. Anyone tried it? Maybe that is the real fix.
Edit:
Oh, I missed there is a new kernel and xcb as well.
Last edited by oz (2013-12-26 14:32:48)
Offline
Same issue for me - Firefox would never last more than an hour, unless launched from terminal. Some sites were guaranteed to crash it (ie. slacker.com).
I updated nvidia and kernel today and the problem appears to be fixed.
Offline
I'm on the new kernel and drivers and had another crash. I'm going to perform a clean install of firefox just to make sure.
Offline
Today Firefox is crashing again... I just did a pacman -Syu and rebooted, but it didn't help.
Even the nightly(2013-11-21) I've build a month ago is crashing.
Here I can crash FF easily by opening PDFs or as suggested by lafmeche visiting slacker.com.
People here are almost sure it's related to Nvidia driver: https://bugs.archlinux.org/task/38085
I'll try to downgrade and see if this helps...
P.S.: Now I get why Linus was mad at Nvidia.
Offline
Google+ crashes it frequently as well, for me at least.
Offline
Today Firefox is crashing again... I just did a pacman -Syu and rebooted, but it didn't help.
Even the nightly(2013-11-21) I've build a month ago is crashing.
Here I can crash FF easily by opening PDFs or as suggested by lafmeche visiting slacker.com.People here are almost sure it's related to Nvidia driver: https://bugs.archlinux.org/task/38085
I'll try to downgrade and see if this helps...P.S.: Now I get why Linus was mad at Nvidia.
I've the same problem with the opensource radeon and intel drivers.
Offline
Yep, I've upgraded to the new kernel and Nvidia driver and I can still consistently reproduce a crash by visiting slacker.com and opening PDFs. It's interesting that people are also crashing using ATI/Intel, it seemed as though Nvidia was one common point between everyone reporting this failure.
Offline
It's interesting that people are also crashing using ATI/Intel, it seemed as though Nvidia was one common point between everyone reporting this failure.
Except smulverine who else had problems with Radeon/Catalyst/Intel? He may be facing another problem.
Lets see what happens... dev's are taking too much time for something that seems not that hard.
I can't criticize them, they are working for free. And i suppose that it's not "that hard", (just "a bit hard") because was a regression. They just have to find the commit from FF26 on, who made this happen.
So far i am happy with Firefox ESR, and I'll not update/upgrade it no matter what, until I'm pretty sure its solved.
Ahh... stuff
Offline
I started seeing this after running pacman -Syu yesterday. Prior to that, I was having no problems. My Firefox version didn't change, but here are a few possibly relevant things that did change:
linux (3.12.4-1 -> 3.12.6-1)
mesa (9.2.5-1 -> 10.0.1-1)
nvidia (331.20-2 -> 331.20-3)
Offline
This has been happening for a few weeks now, makes it very hard to work.
It certainly started the day I upgraded to firefox 26 though.
Sorry I can't provide more information than that, but same as most people I'm using nvidia drivers also.
After the gcc-*-multilib upgrades it seems to have improved a little, but there is still something thats not quiet right.
Originally I thought it was something wrong with my setup, so did a full format and reinstall for Arch, but that didn't help with the Firefox issues, did fix a few other little problems though so not a complete waste of time :-)
Offline
I also have the same issue. Starting from the terminal seems to stop the crashes. When I start from the terminal, I too get the "GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed" error message. Kernel 3.12.6-1, 64-bit, Nvidia 331.20, Firefox 26.2. The only enabled extension is Adblock Edge. I tried a couple of links at the Macy's site and everything worked ok, apart from a raised eyebrow from my wife regarding my apparently newfound interest in handbags.
Offline
I'm still getting crashes even with everything up to date. It worked for a while then now after rebooting it's suddenly crashing all the time again. Something is seriously wrong because it's not just Firefox that is acting strange. Terminals are weird too. For example resizing them does not always update the size within applications (eg. "screen") and often control commands don't work at all (CTRL-Z, etc). VirtualBox is also broken with incorrect permissions on its devs in /dev plus it will not boot XP machines if running under MATE or KDE (works in XFCE though).
It could all just be coincidence but I sense a serious low-level systemic problem.
Offline
Same issue for me - Firefox would never last more than an hour, unless launched from terminal. Some sites were guaranteed to crash it (ie. slacker.com).
I updated nvidia and kernel today and the problem appears to be fixed.
Well, I'm stumped. It worked great for about a day and now I'm back to crashing. It appears mostly random, except for certain sites that are guaranteed to crash. Have tried the following:
- Disabled addons, did not help
- New, clean profile, did not help
- Safe mode seems to work, but have not tested extensively
- Have not had a crash in several hours, launching Firefox from terminal
- Also removed flash, since it was a flash site that was causing my biggest headache, but it still crashes randomly
Last edited by lafmeche (2013-12-28 22:26:49)
Offline
Crashing here too in the same conditions people is saying.
Last edited by josealb77 (2013-12-28 22:42:27)
Offline
3 days of uptime later and Firefox ESR still didn't crashed, you all should try till Firefox problem its solved.
I am using 15 add-ons, 8 plugins, a custom theme, and opening loads of PDF's.
Ahh... stuff
Offline
For me is enough to downgrade to Firefox 25, no need to downgrade to Firefox 24. I have been for a week downgraded to 25 and all worked perfect again, I decided come back to 26 reseting all settings and configurations, deleting personal folder too, and the segmentation faults came back.
Offline
For me is enough to downgrade to Firefox 25, no need to downgrade to Firefox 24. I have been for a week downgraded to 25 and all worked perfect again, I decided come back to 26 reseting all settings and configurations, deleting personal folder too, and the segmentation faults came back.
You had cache. Some people clean it often like me
Ahh... stuff
Offline
The first time I suffered the segmentation faults I already moved the home firefox folder, rebooted and did all kind of tests and experiments. And since cache is placed in that folder it didn't affected. Today I've been using firefox 26 for more than 4 hours and didn't experienced any crash. Let's see how long it lasts.
Offline
I have been noticing this for a while. I can't use Mega, it crashes after a few seconds of logging in. Sometimes it crashes at sites with javascript or flash features, never on "regular" sites.
Offline
I had the same problem. By disabling the chronology saving on Option --> Privacy (it uses cache) Isolved the problem of random crashes.
Offline
After testing various things it seems very likely this is some sort of problem with the graphics subsystem. I don't know if it's the nVidia driver or something in X.org. My "screen" issues, VirtualBox, Firefox, etc all seem to be graphics related.
Anyway, I have been testing Ubuntu 13.10 and no issues whatsoever so far (it's on the 319 nVidia driver though). Well, no issues other than Xinerama is still broken.
Offline
yes, this issue is due to the nVidia drivers, and they have said they will include a fix in an upcoming driver release.
[site] | [dotfiles] | あたしたち、人間じゃないの?
Offline
I was repeatedly encountering this problem -- it would even cause my entire system to lock up sometimes.
I did some research on the topic and ended up turning off hardware acceleration in Preferences->Advanced->General. No crashes since
Last edited by likytau (2013-12-30 05:18:41)
Offline