Fixing Constant Crashing
Hello,
For nearly a year, I've had an issue where Firefox's screen would either go completely black or white, and would only return to normal after switching to another tab - scrolling down would make it go blank, again. Usually about five minutes in, Firefox will crash. I'm at the latest beta version, I've done a reset, and I've disabled Hardware Acceleration before - disabling it would only make it crash faster.
Here is the data from my latest crash:
AdapterDeviceID: 0x0fd4 AdapterVendorID: 0x10de Add-ons: smarterwiki%40wikiatic.com:5.2.1,%7B591f9d2f-ffb2-4bbe-98fc-2fb86649c789%7D:1.157,%7BDDC359D1-844A-42a7-9AA1-88A850A938A8%7D:2.0.17,%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D:30.0,jid1-cwbvBTE216jjpg%40jetpack:2.1.0,jid1-7NbXi2AqS1oUFw%40jetpack:0.2.6,firefox%40ghostery.com:5.2.1,%7Bd10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d%7D:2.6,jid1-xUfzOsOFlzSOXg%40jetpack:4.3.2.1 AvailablePageFile: 4954017792 AvailablePhysicalMemory: 855748608 AvailableVirtualMemory: 400474112 BIOS_Manufacturer: American Megatrends Inc. BlockedDllList: BreakpadReserveAddress: 336920576 BreakpadReserveSize: 37748736 BuildID: 20140515140857 CrashTime: 1400744626 EMCheckCompatibility: true FramePoisonBase: 00000000f0de0000 FramePoisonSize: 65536 InstallTime: 1400292597 Notes: AdapterVendorID: 0x10de, AdapterDeviceID: 0x0fd4, AdapterSubsysID: 21151043, AdapterDriverVersion: 9.18.13.3523 D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+ WebGL? EGL? EGL+ GL Context? GL Context+ WebGL+ ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414ThebesLayerD3D10::Validate(): Failed to create texture Error code: 2147942414 ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384} ProductName: Firefox ReleaseChannel: beta SecondsSinceLastCrash: 123892 StartupTime: 1400717956 SystemMemoryUsePercentage: 89 Theme: classic/1.0 Throttleable: 1 TotalPageFile: 17093877760 TotalPhysicalMemory: 8547893248 TotalVirtualMemory: 4294836224 URL: http://www.tumblr.com/blog/jackmackerel/activity Vendor: Mozilla Version: 30.0 Winsock_LSP: MSAFD Tcpip [TCP/IP] : 2 : 1 : %SystemRoot%\system32\mswsock.dll
MSAFD Tcpip [UDP/IP] : 2 : 2 : MSAFD Tcpip [RAW/IP] : 2 : 3 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [TCP/IPv6] : 2 : 1 : MSAFD Tcpip [UDP/IPv6] : 2 : 2 : %SystemRoot%\system32\mswsock.dll MSAFD Tcpip [RAW/IPv6] : 2 : 3 : RSVP TCPv6 Service Provider : 2 : 1 : %SystemRoot%\system32\mswsock.dll RSVP TCP Service Provider : 2 : 1 : RSVP UDPv6 Service Provider : 2 : 2 : %SystemRoot%\system32\mswsock.dll RSVP UDP Service Provider : 2 : 2 : MSAFD RfComm [Bluetooth] : 2 : 1 : %SystemRoot%\system32\mswsock.dll
useragent_locale: en-US
Isisombululo esikhethiwe
This is what to try, enable one of them, restart Firefox and see if there is still a problem. Then, disable that one and enable the other. Restart. Is there a problem?
Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0All Replies (7)
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
- Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
- Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste that into the "Post a Reply" box.
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Done:
bp-24ba3b8b-451b-48a5-84d3-ae1df2140522 bp-b4b9da4f-ab10-4891-8dba-30e6b2140520 bp-9d8cd20c-2db5-4102-923f-32dab2140516 bp-98fec1b2-bf49-46ab-a025-f17c02140516 bp-26b51a54-8029-404f-bea2-6a7722140515
Start Firefox in Safe Mode {web link} While you are in safe mode; Poke around safe web sites and see if there is still a problem.
Certainly use of Ghostery has been linked in the past with triggering similar crashes, and your crashes are occurring when memory usage is high.
You also use AdBlockPlus that is known to cause memory issues with Firefox.
Try in safe mode as suggested already. Does that prevent crashes ?
Next try with Ghostery and AdBlockPlus disabled is that enough to prevent crashes ?
You have quite a list of addons and it is possible they do not play well together. Try the suggestions and please report back how you get on.
The investigation into the existing filed bugs may not be making much headway at the moment. (STR ?)
For forum cross referencing purposes
- Crash Reports for your CrashIDs
- bp-b4b9da4f-ab10-4891-8dba-30e6b2140520
& bp-9d8cd20c-2db5-4102-923f-32dab2140516 - bp-98fec1b2-bf49-46ab-a025-f17c02140516
& bp-24ba3b8b-451b-48a5-84d3-ae1df2140522 - bp-26b51a54-8029-404f-bea2-6a7722140515
- bp-b4b9da4f-ab10-4891-8dba-30e6b2140520
- Crash Signatures
- # Signature: JSC::Yarr::YarrGenerator<int>::opCompileAlternative(JSC::Yarr::PatternAlternative*)
- Signature: JSC::Yarr::Vector<JSC::Yarr::YarrGenerator<int>::YarrOp, int>::append<JSC::Yarr::YarrGenerator<int>::YarrOpCode>(JSC::Yarr::YarrGenerator<int>::YarrOpCode const&) </li>
- mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | gfxAlphaBoxBlur::Init(gfxRect const&, nsIntSize const&, nsIntSize const&, gfxRect const*, gfxRect const*)
- Related Bugs (+ my comments)
- 814954 REOPENED --- crash in JSC::Yarr::YarrGenerator<int>::opCompileParenthesesSubpattern
+ A prior version of Ghostry was initially involved in triggering some of these crashes. - + none seen
- Bug 986502 - crash in mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | gfxAlphaBoxBlur::Init(gfxRect const&, nsIntSize const&, nsIntSize const&, gfxRect const*, gfxRect const*)
+ memory issue, and I am aware currently ABP is causing memory issues
- 814954 REOPENED --- crash in JSC::Yarr::YarrGenerator<int>::opCompileParenthesesSubpattern
I've tested out safe mode - no matter how many tabs I open, it does not crash, so it seems to be Ghostery and ABP. Are there alternatives to these I can use?
Isisombululo Esikhethiwe
This is what to try, enable one of them, restart Firefox and see if there is still a problem. Then, disable that one and enable the other. Restart. Is there a problem?
There are many alternatives for script and adblocking.
- For instance glance at https://addons.mozilla.org/en-US/firefox/extensions/privacy-security/
You already have quite a few addons installed that could complicate matters.
The ABP issue will potentially be affecting a nearly 20 Million (ADB on Firefox) install base and is something both Mozilla developers concerned with Memory use and ABP developers are now aware of. I imagine in due course changes with ABP or Firefox will improve the situation.
- See Bug 1001426 - 150MB memory usage spike by enabling Adblock Plus
Bug 988266 - Very high style-sets memory usage with AdBlock Plus - Note bugzilla is not a discussion forum so note the ettiquete. If you are interested enough you may consider voting on or subscribing to the bug report. (You will need an email address that will be made public )
You could consider testing out possibilities in a test profile, or you may even manage to work in different profiles for different purposes and reduce problems by having a minimal number of addons enabled in each profile. Multiple profile use is considered an advanced subject and not documented in our Firefox Knowledge Base (KB) (It is in the Thunderbird KB) if you consider that have a look at a prior post I made
Presumably you have no problems at all with firefox in safe mode and with all plugins installed. Also try not in safe mode, but with all plugins and all extensions disabled. (That may for instance indicate a hardware acceleration or graphics issue is also involved)
Note about:memory (type into addressbar, then once open note interactive mouse tooltips) will show Firefox memory use and actually has a button to reduce memory use. Windows task manger will give an overall picture of real time memory use. I mention this because maybe as a workaround you could avoid or predict crashes.