You are not logged in.
Hi all. Since the upgrade to Firefox 26, I've been experiencing lots of crashes. I am currently on 26.0-2, but the issue was also prevalent on 26.0-1. Basically, after starting Firefox, it crashes with no warning, usually either within the first 10 seconds or a few minutes later.
I've tried starting Firefox from a terminal to see any errors and strangely enough, when I do that the crashes are much less frequent (the problem almost disappears and FF can last several hours). I eventually caught a crash in the terminal and it says the following.
(firefox:12326): Gtk-CRITICAL **: IA__gtk_clipboard_get_for_display: assertion '!display->closed' failed
This problem exists for me with both regular Firefox from the Arch extra repo and Nightly from the AUR.
Can anyone shed any light on this?
Thanks!
Last edited by Morley93 (2014-01-21 10:16:22)
Offline
Morley93,
I can't help for the moment, just to say "me too".
Both versions 26.0.1 and 26.0.2.
Normally it crashed in the first couple of minutes, and always when opening PDFs files.
I didn't come to the idea of starting from the command line.
Went back to version 25 and now all is ok.
Mektub
Follow me on twitter: https://twitter.com/johnbina
Offline
Are you visiting any particular website to trigger the crash?
Anything interesting in X log or systemd's journal?
Offline
Could be a problem with one of your add-ons (if you have any). Have you tried safe-mode?
edit No problems here, firefox 26.0-2.
Last edited by WorMzy (2013-12-14 21:49:23)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
So I checked journalctl and my xorg log and there's nothing that seems related in there. In terms of addons, I did notice that logging into the LastPass extension seems to trigger the crash fairly consistently. As Mektub said, a surefire way to trigger it is to try and look at a PDF - even in safe mode, this causes the crash.
Last edited by Morley93 (2013-12-15 00:33:00)
Offline
I have the same problem with version 26. Firefox crashes about 3 seconds after I open a PDF file:
Segmentation fault (core dumped)
Last edited by aero (2013-12-16 00:10:31)
Offline
So do I, it's annoying.
Days ago when I updated to 26.0.2, it seems the problem had been solved. But today it crash again. I have tried pacman -Syu but it still keep crashing.
Last edited by jhaohai (2013-12-16 05:15:58)
Offline
Same problem, really annoying...
Offline
Is everyone here enable firefox sync?
I think i have found the problem. After I disable firefox sync, everything goes fine.
Offline
jhaohai,
I have the problem and I don't enable or use firefox sync.
Mektub
Follow me on twitter: https://twitter.com/johnbina
Offline
jhaohai,
I have the problem and I don't enable or use firefox sync.
Mektub
That's strange. After I disable firefox sync, it doesn't crash anymore.
Offline
The strangest thing for me is that this is a huge problem if I start Firefox from a launcher/menu, but if I start it from a terminal the problem seems to completely disappear.
Offline
The strangest thing for me is that this is a huge problem if I start Firefox from a launcher/menu, but if I start it from a terminal the problem seems to completely disappear.
I've been having trouble starting KeePass these days too. When I attempt to launch it from the GUI, nothing happens. When I attempt to start it from the command line, it often works. I wonder if the KeePass problem is related to the Firefox crashes. Perhaps some underlying library has developed a race condition, and both apps just happen to be hitting it. Running from the command line might alter the timing to the point where things work (with stdout not connected to /dev/null).
Offline
I'm experiencing the same issue. As soon as I open a PDF file, it crashes after a few seconds. It seems to crash less when I start it from Terminal and it does not output anything interesting besides the usual "Segmentation fault" stuff. Really annoying.
Offline
I'm having the same problem.
Firefox crashes with a segmentation fault, usually when viewing a PDF with the built-in PDF viewer but also when viewing Wunderlist website.
Offline
I have the same problem, but it crashes the most when downloading files of any kind. I have also noted that if you launch Firefox from terminal it does not crash, or at least for the time I've been trying it this way.
Any solutions? It's pretty disappointing. I think it could be related with the current working directory when launching firefox, but it's just a guess. For the time I have to use Chromium (which I don't like it too much).
Offline
I have the same problem when I access Facebook (it seems, I can't trigger it reliably).
Firefox either crashes or gets killed due to OOM-killer running because my swap fills to 100%.
Not very helpful I know, sort of a "me too" post, but Firefox 26 on Arch has been the crash-iest version I think I've ever used personally.
Offline
Same problem here. When i try to edit a LastPass Vault entry, the browser closes. Same result opening a PDF file. I've opened the browser from CLI and it seems to work fine.
Offline
Same problem here specially with Facebook, but it does seem to go away when i launch Firefox from the CLI.
Offline
Firefox starts freezing X entirely since version 24.
Can't really put my finger on it so I'm afraid I can't do more than confirm I have the same issue. Sometimes it's just hovering over a URL that does it.
Tried a few things. Switched off hardware acceleration as suggested here:https://support.mozilla.org/en-US/questions/963963.
Disabled sync.
Started with a new profile without any extensions whatsoever.
Nothing seems to help.
I've installed the firefox-nightly build from the AUR and the problem still occurs.
The browser in the tor bundle (Firefox ESR I think) does fine however.
It's a pity since Firefox has been my preferred browser forever on both Arch and Android.
Last edited by smulverine (2013-12-19 03:48:55)
Offline
I have problems running Firefox, too. I have a somewhat similar problem which says, when I run Firefox from within the terminal, the following:
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
For the last couple of days, the browser has been crashing most of the time I try to navigate, and, all the time when I try to open a .pdf file.
Any ideas, suggestions to overcome the issue?
P.S: The only add-on installed is xMarks, which has been doing well until very recently. I do not use Firefox Sync feature.
Edit: When I do "Ctrl+Shift+Del" to clean the privacy cache, again, I have the crashing problem.
Last edited by aytekinar (2013-12-19 07:41:00)
Offline
The strangest thing for me is that this is a huge problem if I start Firefox from a launcher/menu, but if I start it from a terminal the problem seems to completely disappear.
Yep, I noticed the same thing...
And this seems to be a recurring theme for me with Arch. Tomboy launched from the menu results in an unresponsive tray icon. Launched from a terminal? Works perfectly fine! The same was happening for the game Hammerwatch - worked fine if launched directly in a terminal, or if Steam was launched from a terminal, but if I launch Steam from the menu, the game crashes (unless I add LD_LIBRARY_PATH=:/usr/lib/mono %command% into the game's launch options...). I do not know what is going on, but it's really got me wondering about my future with Arch. And that sucks, because I've loved the month or two I've spent with the distro so far, other than these *really* annoying issues. I have searched and searched for several weeks, and come up with no solutions so far. The worst part is, other Arch users say things run fine for them (Hammerwatch players using Arch, posting on the Steam forums, for example). Very frustrating.
Offline
I have the same problem and I don't even have to do anything special. I reopen FF, it apologizes for being buggy bullshit and after a couple of seconds I'm on the desktop again. I use Sync. At the time of the crash only my 4 pinned tabs should be loaded (google+, calendar, owncloud and ampache) perhaps they use some dark magic JS that FF is currently too dumb to parse correctly.
I've been having trouble starting KeePass these days too.
I also had that problem, even before FF started acting up. I've settled for keepassx2-git (AUR) which happens to be way faster and sufficiently feature complete. So far I only noticed the keygen being comparatively incomplete.
EDIT: Starting from console the problem completely disappears. FF runs stable without any problems.
Last edited by Chais (2013-12-19 22:12:20)
--
Chais
Offline
I have the same problem with only Firefox 26.0-2 and Nvidia 331.20-2 --- Firefox will close on certain websites with map-images when I try to click on one.
(I have not any issues with PDF files)
I do not have this problem with Firefox 26.0-2 with other graphic drivers (ie: laptop, desktop, using the nvidia 304xx drivers).
All systems are using linux 3.12.5-1 and all are under i386.
So it seems the problem (FOR ME) is the Nvidia 331.20-2 -- ????
http://www.macys.com --- (US Store) any click on main site will cause segmentation fault (firefox disappears).
(but again this only happens to the one desktop with the Nvidia 331.20-2)
Last edited by Kilzool (2013-12-19 16:49:15)
Offline
Same problem here, extremely annoying. Apart of segmentation faults, I also experienced session loss, feels like back in 1999 already
I'm on kernel 3.12.5-1, firefox 26.0-2 and nvidia 331.20-2, firefox sync is disabled.
Offline