Firefox crashes
Hello there, I'm running a fresh install of Linux Mint 15.
uname -a Linux Zacs-computer 3.8.0-34-generic #49-Ubuntu SMP Tue Nov 12 18:02:44 UTC 2013 i686 i686 i686 GNU/Linux
Firefox version is 25.0.1, which came along with the system.
It keeps crashing randomly and unexpectedly. It seems to be due to a "segmentation fault". That's all I get from a terminal at the moment of the crash. This is the latest crash report: bp-dbc53706-21a7-4524-8772-167242131204
I'm a regular desktop user of Linux, so I'm not very good at solving bugs by myself. The system is updated, firefox is updated. I tried to check hardware acceleration, but didn't really find it. I don't think I have this option. My machine is a bit old an Intel D946GZIS, with a celeron processor.
Firefox is my favourite browser, and I'd really like to stick to it. Any help will be appreciated. If you need any other information, please feel free to ask me. Thank you very much! Zac.
All Replies (13)
Try to surf as much as possible with all plugins disabled and in Firefox's safemode. Does that prevent the crashes ?
- This article includes instructions to turn off Hardware Acceleration (HA) in Firefox. If you are outside safe mode it may help to have HA disabled.
- Try: Holding down the shift key when launching Firefox, that should put it in SafeMode
See Diagnose Firefox issues using Troubleshoot Mode
Note one of the features of Firefox's safe mode is that it turns off HA
If Firefox continues to crash please paste into your next report thee or four recent crash reports, preferably from safe mode crashes with plugins disabled.
For forum cross referencing purposes
- Report for your Crash ID bp-dbc53706-21a7-4524-8772-167242131204
- Crash Signature: nsDisplayList::FlattenTo(nsTArray<nsDisplayItem*>*)
- Related bugs: Bug 847008 (inactive first reported in Fx19 & 20)
Edit
- Report for your Crash IDs
bp-7aa1a1b7-6006-415c-9ee2-0ff292131225
bp-2be98b1e-a198-4ec3-b423-8f15d2131225
bp-8f1bc4ff-2e25-41e0-9d95-852212131225- Crash Signatures
libxul.so@0xf15261 | nsThread::PutEvent(nsIRunnable*)
nsINode::GetProperty(nsIAtom*, tag_nsresult*) const
js::gc::MarkObject(JSTracer*, js::EncapsulatedPtr<JSObject, unsigned int>*, char const*) - Only bug mentioned Android related. Not frequently seen signatures.
- Crash Signatures
Modified
Hi,
Thanks for your input.
To be honest, I was expecting a bit more than this.
That was a pretty standard reply, nothing you can't find in your own website.
I've been surfing in safe mode, and the problem persists. Firefox keeps annoyingly crashing all the time, even in safe mode.
I've already tested my RAM for errors with memtester linux utility. It presented no errors.
My latest crashes:
bp-7aa1a1b7-6006-415c-9ee2-0ff292131225
bp-2be98b1e-a198-4ec3-b423-8f15d2131225
bp-e103a81f-ab22-4600-bfd8-789962131225
bp-8f1bc4ff-2e25-41e0-9d95-852212131225
bp-412d81f2-c13a-49fe-a30d-8ea862131225
bp-be2db95e-68f4-41f1-b5a1-ae7a72131225
Please, help me solve this annoying problem.
Thank you very much!
Zac.
Did you check for issues caused by plugins?
Something funny has just happened. After I saw your post, I went for testing and disabled all the plugins.
One minute after I did that, firefox crashed! :)
bp-3adac377-7b43-4b81-ad84-2194c2131226
So apparently it's not a plugin-related issue.
Any other suggestion?
Thanks
How much physical memory do you have and what is the usage and free memory when you check that in the System Monitor?
You can also check the about:memory page.
Hi, thank you for helping me out.
I have 2,0GiB of RAM.
When I look at GUI System Monitor, it says the system is using about 600MiB of those 2,0GiB.
There something strange here. When I use the command free, with the option -m, it shows me another reality. I wanted to show you the whole output, but there's no space here for .txt code. That's pretty bad, isn't it? You also can't attach a .txt file. This html formatting messes up the whole data! So how could we show you guys some code?
Anyway, it says I have a total of 2006MiB of memory, and that 1560MiB is being used, thus leaving 445MiB free.
buffers: 108
cached: 840
What do you say of that? And why this discrepancy between the two analysers?
I wanted to attach a memory report, from about:memory, but couldn't. I confess I can't analyse such technical stuff.
It would be nice if we could attach .txt files or if we could post their content in a special space designed for them as you see in many Linux forums.
Thank you very much.
Hi Zacura, I will split the replies
Something funny has just happened. After I saw your post, I went for testing and disabled all the plugins. One minute after I did that, firefox crashed! :)
bp-3adac377-7b43-4b81-ad84-2194c2131226
So apparently it's not a plugin-related issue. Any other suggestion?
I did suggest in my first post that you tried in safemode and with all plugins disabled and then posted the crash IDs from any such crashes.
I hoped that may either prevent crashes or produce a more useful set of Crash IDs,
bp-3adac377-7b43-4b81-ad84-2194c2131226 apparently is not a safemode crash with plugins disabled.
Modified
Text files. Rarely of much use on the forum and as you say no proper facilities for text or code.
It would be nice if we could attach .txt files or if we could post their content in a special space designed for them as you see in many Linux forums.
For short extracts use the <pre></pre> tags. Not perfect or user friendly but it helps
- e.g. <pre>some text line, [Rtn] another</pre> gives
some text line, [Rtn] another
- or do similar by adding a preceding space on each line
a short line a wrapped line bbbb bbbbb bbbbb bbbb bbbb bbbbb bbbbb bbbb bbbb bbbbb bbbbb bbbb bbbb bbbbb bbbbb bbbb another short one
If you really need to add long text then use Pastebin and link to that
The gzippedfiles from about:memory just can not be handled, consider something like dropbox.
IIRC I suggested it be added as a facility to the forum and that was rejected a an edge case scenario.
I see it as chicken and egg case:
→ No one uses about memory the output is difficult to interpret. →
We do not need to provide a facility to attach files so that we can find someone to interpret them, because no one wants to use about:memory →↑
Modified
John, I apologize. I think I confused plugins with add-ons, thinking they were all the same thing. So I was surfing in safemode thinking that was enough, but actually I still had to disable the plugins. Regarding my last crash ID, I'm sure I was with all plugins disabled, but possibly not running in safemode. So now I got the idea. Safemode + disabled plugins. Sorry about that. I've been surfing that way for some hours now, without a crash. I'll have to wait a little longer though, to be sure firefox won't crash under these conditions. If it doesn't I will test it by enabling plugins each at time to see what happens. That might take some time. If it does crash, however, I'll provide you with more useful crash IDs. Alright?
Regarding 'proper facilities for text or code', thank you for the instructions. That will be more than enough, I hope.
Once more I apologize for misunderstanding your first instructions, and thank you very much for your help!
I'll be back!
:)
Thanks for posting back.
I hope you sort it out fully.
Maybe it is a couple of plugins together or one that needs updating.
Bad news... Firefox has just crashed in safemode, with all plugins disabled.
Here is the ID:
bp-5670bbbf-e0a9-49e4-b48f-ae5b62131227
If it happens again, I'll post the respective IDs.
Thank you!
Another crash, under the same circumstances: bp-c89c1198-cb98-4d41-bee3-f07192131229
Any idea of what is causing the issue?
Thanks!
All I can say is try a fresh install of Firefox, I do not see any info that helps me in the crash report.
When reinstalling make sure you do NOT remove the Firefox profile files,but do remove the program folders and files.
There is something else you could try. Install and use the Mozilla Firefox browser as an additional browser on a per user basis. If nothing else it will be a useful stopgap measure and gives you something to use if the main browser crashes.