Frequent crashes, different machines, FF 24-30
Since using Firefox on Windows 7, I have been encountering crashes and hangs that all exhibit the same symptoms. Large blocks of the screen go black. Moving the mouse restores the images, then they go black again. It happens most quickly when scrolling through images (like from a Google image search). Sometimes I will kill FF, but other times it crashes before I can kill it. The Windows eventvwr doesn't record the crash.
I've reinstalled FF from scratch. Reimaged my machine with Windows 7. Bought another laptop installed Windows 7 from scratch and the crashes continue. I've started Firefox in safe mode, still crashes. It usually takes a couple of hours of use before the video goes black and it crashes, almost like a memory leak.
This has been going on literally for months.
Based on a problem someone else here reported, I've pasted the last few crash ID's below.
bp-dcbe53c4-9d14-4cbe-a195-86ba12140701 7/1/2014 9:58 AM bp-4e6d0b65-21d6-4424-a6df-d99442140630 6/30/2014 9:34 AM bp-57910066-00e1-4d64-8fec-9debc2140626 6/26/2014 3:24 PM bp-9926193c-3346-4be0-80bc-ebf892140625 6/25/2014 1:41 PM bp-685a8aad-8006-436c-accf-f23b72140625 6/25/2014 12:13 PM
I suspect something could be going wrong with Firefox's graphics handling. The crash Reports are showing high memory usage by Firefox.
Not too much I can say other than they are top crashes and are being worked on. Perhaps watch the memory usage levels. Using the buttons in about:memory may help.
Test in Firefox's Safe Mode and with all plugins disabled does that prevent crashes ? (Thought - Hardware acceleration is turned off in Safe Mode does that help ? )
- Troubleshoot Firefox issues using Safe Mode
- Disable or remove Add-ons
- Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems
I will tag this question as escalate. Someone from HelpDesk may be able to offer better advice, but that may take a few days.
For forum cross referencing purposes
- Your Reports for Crash IDs (& memory %)
- bp-dcbe53c4-9d14-4cbe-a195-86ba12140701 (89%)
- bp-4e6d0b65-21d6-4424-a6df-d99442140630 (95%)
- Crash Signatures
- Signature: OOM | small
- Signature: gfxContext::PushClipsToDT(mozilla::gfx::DrawTarget*)
- Related Bugs
- None (But the current #1 Fx 30 crash)
- Several. Includes
Bug 1011864 - Mozilla Firefox 29.0 crash (pointing to Null ) with window.open and very large sizes (PushClipsToDT signature)
- Bug 1029124 - Cap the size of window that can be specified by window.open
Bug 1029125 - Cap window sizes at the widget level
- Bug 1029124 - Cap the size of window that can be specified by window.open
Thank you for your response and time. I thought it seemed like a memory leak or something because it tends to happen after I've been using FF awhile, and I've noticed that the RAM usage according to taskmon is 1.3-1.4GB of RAM in use when it crashes. I've run it in safe mode but it doesn't make a difference.
Thanks again for any help.
HI rtav, There are some troubleshooting steps you can take to minimize memory while the crash issues are being worked on.
However it also looks like there is a new signature that is associated with these crashes, no longer related to : Signature: gfxContext::PushClipsToDT(mozilla::gfx::DrawTarget*)
If I may ask what video player this happens in or a webpage this happens in? The extensions look to have to do with xpconnect or xpi?
You can try to disable hardware acceleration in Firefox.
- Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
You need close and restart Firefox after toggling this setting.
Create a new profile as a test to check if your current profile is causing the problem.
See "Creating a profile":
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test.
I'm not using a video player with Firefox. The crashes occur while browsing pics in Google images, or scrolling quickly through Facebook pages (I can replicate the crashes at will). No video player is being used.
I've tried disabling hardware acceleration manually, the crashes still occur.
I've run it in safe mode, the crashes still occur.
I've uninstalled FF, reinstalled FF, bought a new laptop and installed FF on it clean - the crashes occurred as expected.
Hi rtav, We understand that you are not using a video player, but that the crash occurs while browsing images in Google search or Facebook. What is interesting is that the crash reports have an up time of about two hours and it runs out of memory when allocating 256kb, which is not alot, but it was already using 89%. And the other crash with a different signature is back up to 95% John99 mentioned this and the "gfxContext::PushClipsToDT(mozilla::gfx::DrawTarget*) " signature is currently being worked on, which is also an out of memory crash that is on pages with large graphics as you are experiencing.
Does the new laptop have the same graphics driver as the first computer's troubleshooting info, or was this done before?
If not, I also found that you may need to update your graphics driver: [Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0) ,] make sure it is not blocked https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#Intel_cards or temporarily disable layers.offmainthreadcomposition.enabled in about:config.
Hello and thanks for your analysis.
The laptop I'm using now has an Intel HD Graphics Family chipset, using driver version 220.127.116.1172. It is a Lenovo Ultrabook quad core Core i5 with 8GB RAM running Win 7 SP 1. My older laptop (a Lenovo also) that had the same crashes uses an Intel HD Graphics 3000 chipset with driver version 18.104.22.1683. According to my attempts to update the driver software, the drivers are current on both systems.
I think I found it, in your troubleshooting info: windowLayerManagerType: Direct3D 10
In the link of blocklisted drivers in the previous post:
"We block Direct3D 10 features (including Direct2D) on buggy installations where the Intel driver version reported in the Windows Registry is not equal to the version of the driver DLL, igd10umd32.dll/igd10umd64.dll. See bug 590373. "
The newer veriosn 9.xxx has not been blocked.
After further investigation with the crashkill team, can we please request a few memory reports when you start to see this issue.
To do this please follow these instructions:
- Open the [about:memory] page in the Firefox url bar
- Click Save Memory Reports "Save Memory and Save"
- Save the file and share a link or you can attach it here: http://pastebin.mozilla.org/
Rachel, not sure moziilla.pastebin * is a good idea, other than for small fragments of the text report. AFAIK mozilla.pastebin does not accept attachments so .gzip files can not be attached. I do remember suggesting we allow attachment to sumo answers but idea was rejected.
- see https://blog.mozilla.org/nnethercote/2013/04/10/gzipped-json-is-now-the-preferred-format-for-attaching-memory-report-data-to-bugs/
- [SUMO ENHANCEMENT] Allow attachment of gzip files /forums/contributors/709551
I would have thought if we were to allow gzipped files, but worried about exploits we could run a simple test to check they appeared to be memory reports. If we actually start trying to answer memory related questions and crashes the files could be of use. Possibly Kadir's opinion would change if it were shown to be useful. As for the privacy issue would a reminder to view the files before attachment solve that?
Yes, I can ask about this next week as well at least for an alternative. I will PM you. I have seen bugzilla used for memory reports.
I have created a bug report for this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1034254
May we request memory reports from rtav or any other users who are experiencing this crash. Currently it is one of the top crashes and more information is needed.
Please attach the reports to the bug, you will first need to create a bugzilla account and please see the etiquette before posting to the bug, thank you!
FF does not respond or is the collapse in safe mode when content on the page becomes too much with the need to scroll further. Of RAM 16 GB W7 64. Download ram somewhere on 6 GB (using Firefox approximately 3 GB) and is it possible to find out the problem on the page mozilla crash reports?, there title Firefox 30.0 Crash Report [@ OOM | small ]. Please tell me what could be wrong?
bp-6828228e-b055-44b4-99dc-902602140716 bp-5f990905-9a9e-4c9c-8fcc-646f62140712 bp-4fb04fb6-2d54-4809-b9d9-7e05e2140712 bp-51bfe937-1bc5-4607-a77d-c36f32140702 bp-709fcf02-9639-4b36-9927-b598f2140627
browser.cache.disk.capacity 1048576 browser.cache.disk.smart_size_cached_value 358400 browser.cache.disk.smart_size.first_run false browser.cache.disk.smart_size.use_old_max false browser.cache.memory.capacity 0 browser.cache.memory.enable false
Disk cache device Number of entries: 14964 Maximum storage size: 358400 KiB Storage in use: 114868 KiB Cache Directory: C
Offline cache device Number of entries: 0 Maximum storage size: 512000 KiB Storage in use: 0 KiB Cache Directory: C
First one is a flash crash and the rest are out of memory errors. Even though it looks like 31% of the available system memory.
Does Flash require offline storage? I know in the Global settings you can clear the stored preferences and storage of the Flash plugin, if you enable the cache temporarily, does it still crash?