Firefox crashes clicking on links
I can easily reproduce the crash on the following two sites:
http://www.libero.it/ while reading email (requires an account)
http://www.eu-shop.hannspree.com/ while surfing (no account required)
To make reproduction easier, lock as application 3 or 4 tabs with big apps like gmail and google calendar. Restart FF and, on a new tab, go to http://www.eu-shop.hannspree.com/ and click on one of the products at the bottom of the page.
This is not needed to reproduce the crash, it only makes it easier to reproduce.
I've done all updates, restarted without plugins, created a new profile, and tested nightly. It still crash.
모든 댓글 (7)
Worksforme - so I guess something strange on your system, or possibly malware
Using precise 12.04TS like you but when I try the linked site in Canonical Firefox Aurora fx15.0a2 or in Mozilla's fx13.0.1 no crash.
AFAIK Canonical Aurora will not generate mozilla's crash reports so either deal with as an Ubuntu bug or better still try the Mozilla Release or Nightly and paste in Crash IDs in your next reply.
- Install Firefox on Linux
- Troubleshoot Firefox crashes (closing or quitting unexpectedly)
- Improving Ubuntu: A Beginners Guide to Filing Bug Reports
http://ubuntuforums.org/showthread.php?t=1011078 - https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20%28using%20gdb%29
I'm not using FF from Ubuntu repositories. I always download it from www.mozilla.org, to be sure I can generate mozilla's crash reports. You can check one of the following crash reports (I have tens of them):
- https://crash-stats.mozilla.com/report/index/bp-f9623e43-d0e5-4ab9-a992-a6fc92120717
- https://crash-stats.mozilla.com/report/index/bp-31cf5afc-f081-4ea5-863d-d810a2120717
- https://crash-stats.mozilla.com/report/index/bp-b970e105-675d-4f47-9481-f8f252120717
I can reproduce the same crash on two other computers, all with Ubuntu-12.04.
Unfortunately, sometimes, you must use the site for many minutes to reproduce. The procedure that I have outlined above, makes it crash instantly very often.
As a workaround try turning off hardware acceleration when using those sites, or blocking the video content.
Not sure I understand the situation, and do not have time to read up on it today, but it appears to be a known graphics issue with linux that is being investigated.
Thanks for your help John99.
I've turned off hardware acceleration, but it still crashes even restarting with plugins disabled: https://crash-stats.mozilla.com/report/index/bp-970c958d-866f-4090-894e-f92082120717
Sorry for the delay in getting back to you, I was forgetting about this.
I do not see much action on any of the related bugs. I do note that on one there is a suggestion to reset some of the plugin prefs to default values.
- I suggest it is worth trying that to see if it helps.
To reset the prefs- navigate to about:config by typing that into the address bar
- accept any warning that appears
- you will get a long listing, to narrow it down type into the search bar
dom.ipc.plugins - you may wish to make a note of any that are NOT set as default values and make a note of the value in use (they will copy)
- now right click any that are not default and reset them to default values
- restart and check that they are now all at default settings,
then see if crashes stop ?
- If not it is probably worth filing a bug report yourself from one of the Crash Report pages.
For forum cross reference purposes
All above reports same signature
- reports for CrashIDs: 970c958d-866f-4090-894e-f92082120717
- Crash Signature: TouchBadMemory | mozalloc_abort | NS_DebugBreak_P | X11Error
- Related Bug s 733322, 754911, 589546, 733324, 733325, 751163, 733323
I've checked: all dom.ipc.plugins.* values are already set to default values.
I've also tried to restart with all plugins disabled: it crashed.
Here are the last CrashIDS:
- bp-81450636-45e1-4b25-a5aa-72eb92120730
- bp-6817d22d-5ae9-4def-9ac5-c3f632120730
- bp-9c531fe9-b6cc-4d58-a837-dd8912120730
- bp-a8cb6d46-37c1-424d-bc1c-a17b02120730
Sorry Marcello no other ideas.
Please File a bug from one of the Crash ID Reports. Maybe someone will reopen bug 692753
I have no ideas but hopefully one of the bug triagers will be able to help.