This thread was archived. Please ask a new question if you need help.
Firefox 30.0 also crashing
I thought the new release would fix the frequent crashes I've been experiencing, but Firefox 30.0 is also crashing with the same graphics acceleration issue. Does anyone know when this bug will be fixed?
Yes, I saw that (... PushClipsToDT ...) is still high on the crash stats, so I didn't think it was worth suggesting to others to try out the beta channel. But 31.0 is working for me and hopefully it will continue to do so. :)Read this answer in context 👍 0
All Replies (20)
Also, with Firefox 30.0 I'm also getting this error which I've never had with any of the previous releases. Why is Flash suddenly causing problems? Is this related to the graphics acceleration issue? Should the plugin-container.exe be disabled? And if so, how do you do that?
Problem Event Name: APPCRASH Application Name: plugin-container.exe Application Version: 18.104.22.16862 Application Timestamp: 5387f37a Fault Module Name: mozalloc.dll Fault Module Version: 22.214.171.12462 Fault Module Timestamp: 5387c49f Exception Code: 80000003 Exception Offset: 0000141b OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 3081 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
And I noticed in the plugins that Shockwave Flash 126.96.36.199 is set at 'Always Activate' but the others are 'Ask to Activate'. Is this OK?
Sorry if I sound like a moaner, but I live in an area that doesn't provide unlimited Internet access, so every crash is costing me MAJOR data usage. So, if these crashes are going to be regularly occurring for the foreseeable future is there any way I can save my cached web content (by copying and restoring the cache folder?), so web pages won't need to redownload again and again and again? If this is not possible and no fix is in sight, then I am going to regretfully have to change browsers as I just can't afford to lose this much data.
Modified by Vici
EDIT 2: SPOKE TOO SOON. HAPPENS WHEN RELOADING A PREVIOUS SESSION USING SESSION MANAGER ADD-ON. BECOMES "NOT RESPONDING" EVEN THOUGH THE MOZILLA ARCHIVE FORMAT 3.0.2 IS DISABLED
EDIT: I DISABLED ADD-ONS AND RE ENABLED THEM ONE AT A TIME. SEEMS TO BE CAUSED BY "Mozilla Archive Format 3.0.2"
FF is completely unusable. Posting via Safari.
EVERY time I try to open a page, this error causes FF to become Not Responding:
6/11/14 4:50:05 PM kernel Data/Stack execution not permitted: firefox[pid 6174] at virtual address 0x128dea000, protections were read-write 6/11/14 4:50:13 PM kernel Data/Stack execution not permitted: firefox[pid 6174] at virtual address 0x128deb000, protections were read-write 6/11/14 4:50:17 PM kernel Data/Stack execution not permitted: firefox[pid 6174] at virtual address 0x128dec000, protections were read-write 6/11/14 4:50:21 PM kernel Data/Stack execution not permitted: firefox[pid 6174] at virtual address 0x128ded000, protections were read-write
forever. The above error is from clicking on the email notification link.
Modified by VerizonSucks
Anyone with any answers or suggestions? Firefox has never let me down before, but this constant crashing it's doing now is driving me crazy!!!
Modified by Vici
Hi Vici, I do not want to recommend to disable the plugin container again, but yes this bug is still being worked on. I have added the stacktrace to the bug report. Currently it is depending on 3 other bugs as well as a error exploit. At this time I do not know when this will be considered fixed.
This is the current test case https://bug1011348.bugzilla.mozilla.o.../attachment.cgi?id=8423540
Edit spelling: have you tried disabling d2d in about:config?
Modified by guigs
Thanks for the reply, guigs2. I'm actually glad to hear that this bug is still being worked on as I was starting to think it was a problem on my end.
Disable the d2d? What's that and how do you disable it? Thanks again, guigs2.
Edited to add: As 30.0 was still crashing I've upgraded to 31.0 beta update channel. Is this OK?
Modified by Vici
I Googled d2d - yes, it's already disabled in about:config.
Modified by Vici
I can see this is all very frustrating. I worry firefox is going to lose users. Mainly XP users, due to this unresolved Firefox issue. Unfortunately I guess it is now given lower priority than ever because XP itself is unsupported. XP is still widely enough used for MS to back port a IE fix for XP after XP EOL though
XP gets the security fix after EOL
Even though Windows XP is no longer supported by Microsoft and is past the time we normally provide security updates, we’ve decided to provide an update for all versions of Windows XP (including embedded), today. We made this exception based on the proximity to the end of support for Windows XP.
DOES IT CRASH IN SAFE MODE AND WITH ALL PLUGINS DISABLED ?
- Have you tried that ?
- If it does crash have you provided a Crash ID (And can you provide another one please a very recent one from Firefox30 or Beta)
I stress this because it is important. I know you will not want to use Firefox routinely like that but does it crash. If not then what about in safe mode with every plugin except FlashPlayer disabled.
- Again if that crashes please provide a very recent crash ID
I am not sure you ever provided full troubleshooting information, but you could routinely be running with >10 addons enabled.
Beta Channel (here) Updating to the beta channel is probably a good idea. The beta channel is pretty stable. You get the fixes 6 weeks early. Despite the name the Firefox version is more like a Release Candidate, it is the final testing before Release (Firefox will already have had six weeks each on the Nightly & then Aurora channels)
Test Case TRY this Please actually try that test case. Click on the link above and open it in a new tab or window. You will get a slider and a little symbol and writing underneath it. If you slide the slider the graphic will grow, that should cause Firefox to misbeave or even crash.
- Does that crash your Firefox ? or at least cause it to mis behave.
- If you get a Crash using that especially if that is the only tab open please post the Crash ID
In fact I note from the notes within the test case it may not even produce a Crash of Firefox on Windows
Always Activate You would probably be better setting it to always ask. You are having problems, and you are trying to save bandwidth.
Crash signature & Previous Thread For the benefit of others note this problem is long running and has been seen and reported by viki previously
- see Why does Firefox 29.0.1 keep crashing? /questions/1002989#answer-584243
- Related bugs
Bug 805406 - crash in gfxContext::PushClipsToDT with Direct2D 1.1 (d3d11.dll 6.2 or 6.3)
Bug 1011348 - Crash/freeze when rendering certain private-use characters at font-sizes greater than about 1300% (The one with the testcase)
Hi Vici, Crashkill team followed up with me on this bug. Currently its an out of memory error.To manage your memory you can regularly go to [about:memory] and clear unused memory. Please also see these troubleshooting steps: Firefox uses too much memory or CPU resources - How to fix
Please also post back with your results! It will help other users.
Rachel Is about:memory likely to help ? I suspect I have seen other crash threads where crashes also did not show high memory usage.
Look at some of the crashes we know vici had With Signature: gfxContext::PushClipsToDT(mozilla::gfx::DrawTarget*)
System Memory Use Percentage
Thanks for the replies everyone. This may change (hopefully not), but since I've updated to Firefox 31.0 Beta Channel (which has been a couple of days now), I've had no crashes. Has there been a significant update with Firefox 31.0?
About the memory. Sorry, bit of a techno dunce, but I've had a look and I don't know what to click on for free memory. What is GC, CC? And what would happen if I clicked on 'Minimize memory usage'? And would this help? As John says, my memory usage was not high.
Modified by Vici
Sigh... Spoke too soon. Just had a crash with Firefox 31.0, plus another plugin-container.exe error. :( Gone back to Firefox 30.
I've tried out the Test Case with Firefox 30 and 31. Nothing happened when I moved the slider up and down.
Modified by Vici
Oops. Sorry, it's a different error.
Firefox 31.0 Crash Report [@ JS::PersistentRooted<JSObject*>::PersistentRooted<JSObject*>(JSContext*, JSObject*) ]
Modified by Vici
I noticed your last crash signature is now the number one in the crashing league, but it may well be a bit of a catch all. I am hoping that top frequency may in fact help in that it should be given a higher priority.
By the way if you are needing to install different Firefox versions you could consider leaving both Firefox Release channel & Firefox Beta channel installed. They need separate profiles but you could have a new test profile and a standard working one and choose which to use with which version as they start up. (They will benefit from a separate shortcut icon as well.)
Why not whilst you have Beta installed create a new test profile now. Leave that with no extensions and disable all plugins. Does that still crash then, and if so what is the Crash ID.
- Profile Manager - Create, remove or switch Firefox profiles_creating-a-profile
We can give further details if you go down that route and need help.
Meanwhile Reinstall the Release, but do a custom install and install it in a folder alongside the current one so if the beta is in a folder called Mozilla call the folder something like Mozilla-Release
Should the problem turn out to be a problem with Firefox (Rather than say some third party software/hardware or malware issue) any fix is likely to be seen six weeks earlier if you have the Beta available.
D2D and other problems
You are not alone with having problems with graphics on Recent Firefox Releases
Firefox is unbearably slow after updating to version 27
70 replies, 567 have this problem , 25165 views
Disabling D2D worked for that up until Firefox 27 but not since
- Summary /questions/985969?page=3#answer-546599
- Related bug Bug 973149 - Animations cause CPU Kernel mode overhead
- Crash ID 2eac27cc-2672-4ee8-bfb5-552332140614
- Crash Signature JS::PersistentRooted<JSObject*>::PersistentRooted<JSObject*>(JSContext*, JSObject*)
- Memory 25%
Thanks for all the help, John. Glad I'm not the only one having problems, but I just checked out the crash stats and I couldn't see my crash signature - Firefox 31.0 Crash Report [@ JS::PersistentRooted<JSObject*>::PersistentRooted<JSObject*>(JSContext*, JSObject*) ] - the no. 1 is _VEC_memzero | _VEC_memzero with gfxContext::PushClipsToDT(mozilla::gfx::DrawTarget*) at no. 3.
Also, I did a complete uninstallation and reinstallation of Firefox about 2 weeks ago and the new profile started crashing with the same crash signature - gfxContext::PushClipsToDT (no extensions and all plugins disabled), so I don't think there's anything wrong on my end as nothing has changed and I've been using this computer for years. Anyway, I'll try (not very techno) and create a new test profile for the Beta Channel and see if any more crashes occur. Thanks again.
Modified by Vici
Looks like there are couple different things related to things being too big Please double check they have turned hardware acceleration off, the crashes are still detecting it on.
Uninstall Advanced System care may have also messed up the registry, this module is: ASCUrlScanner.dll
I've checked again to see if hardware acceleration is turned off and it definitely is.
Are you talking about the extension Advanced SystemCare Surfing Protection? I've had it installed for ages and it's never caused problems before. Is it now? And if so - should I turn it off?
It is worth noting that although it may not show this, using Firefox's Safe Mode should disable Hardware Acceleration.
Thanks for the tip, John. :) But after all the problems I had with Firefox 30.0 I went back to Firefox 31.0. It's been 11 days now since I upgraded and the browser has not crashed. Hopefully, this will continue. :)
OK Vici that is good news. Lets hope it keeps working.
I checked the e crash signature you often get (... PushClipsToDT ...) and I do not see it dropping off rapidly on the latest Beta versions of Firefox. Obvioulsy the Beta does not contain some fix that helps everyone. If it is working for you at present by using the Beta channel that is good.
Thanks for the update.