Closed
Bug 796910
Opened 12 years ago
Closed 11 years ago
Mozilla Firefox Not Responding
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 824952
People
(Reporter: tmptgr, Unassigned)
References
()
Details
(Keywords: hang, perf)
Attachments
(9 files)
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC LM 8; .NET4.0C; .NET4.0E; InfoPath.3)
Steps to reproduce:
I was reading Slashdot and then opened a new tab for a Flash demo that played fine the first few times.
Actual results:
The entire browser froze up.
Expected results:
Ice and reload the offending tab(s) instead of forcing the user to kill and restart the whole frickin' browser.
Version 15.0.1.4631. Crashes are critical. Judging by the stack of the firefox.exe thread that's hogging a CPU core, the GC is stuck in a loop:
mozjs.dll!JS_GetNaNValue+0x61
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!?js_DateGetYear@@YAHPAUJSContext@@PAUJSObject@@@Z+0x197
mozjs.dll!JS_TraceRuntime+0x1d5
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!js_AddRootRT+0x5f2
mozjs.dll!JS_TraceRuntime+0x1d5
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!JS_GetNaNValue+0x50
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
Mostly trying to clean up this thread:
mozjs.dll!JS_GetNaNValue+0x61
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!JS_GetNaNValue+0x61
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
Killing the Flash plugin exe made the plugin container stop working, but the most occuring stack didn't change:
mozjs.dll!JS_GetNaNValue+0x61
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
Hangs are worse than crashes because they keep wasting resources.
I hope these stacks are of any use and if not, please tell me how to improve them. Process Explorer using C:\Windows\system32\dbghelp.dll (version 6.1.7601.17514) and symbols path: SRV*I:\symbols*http://msdl.microsoft.com/download/symbols;SRV*I:\symbols*http://symbols.mozilla.org/firefox
Comment 4•12 years ago
|
||
Do you have a URL that exhibits this? If so, place it into the URL section of this bug.
Could you try "Running the profiler"[1] in Nightly and provide the profile for analysis?
Is your Flach plug-in updated[2]?
1| https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler#Running_the_profiler
2| http://www.mozilla.com/en-US/plugincheck/
Flags: needinfo?(tmptgr)
I regularly use the plugin check, and think i am using the most recent Flash (.278 or something).
I don't have a specific URL, but just now it happened as i tried to post an image on Facebook:
mozjs.dll!JS_GetNaNValue+0x61
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!JS_NewExternalString+0xb6d
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!JS_TraceRuntime+0x18f
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!JS_NewExternalString+0xb6d
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!JS_InitClass+0xa31
mozjs.dll!JS_SetGCParameterForThread+0xf129
mozjs.dll!JS_TraceRuntime+0x18f
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!JS_NewExternalString+0xb6d
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!JS_SetGCParameterForThread+0xeed6
mozjs.dll!JS_TypeOfValue+0x8607
mozjs.dll!JS_SetGCParameterForThread+0x114de
mozjs.dll!JS_TypeOfValue+0x8607
mozjs.dll!JS_TypeOfValue+0x8655
mozjs.dll!JS_SetGCParameterForThread+0x1905b
mozjs.dll!JS_GetDebugMode+0x35d
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!JS_NewExternalString+0xb6d
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
mozjs.dll!JS_TypeOfValue+0x34e0
mozjs.dll!JS_SetGCParameterForThread+0x14195
mozjs.dll!JS_TypeOfValue+0x63eb
mozjs.dll!JS_SetGCParameterForThread+0xf31b
mozjs.dll!JS_TraceRuntime+0x1be
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!JS_NewExternalString+0xb6d
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
Killing the plugin-container.exe doesn't help unfreezing it (at physical usage 81.05%, after closing Outlook 2010 and Paint.NET):
mozjs.dll!JS_SetGCParameterForThread+0x19520
xul.dll!JSD_GetScriptFunctionId+0x3f18b
mozjs.dll!JS_TypeOfValue+0xae41
mozjs.dll!JS_TypeOfValue+0xa5d6
mozglue.dll!?ToShortestIeeeNumber@DoubleToStringConverter@double_conversion@@ABE_NNPAVStringBuilder@2@W4DtoaMode@12@@Z+0x1537
mozjs.dll!JS_TraceRuntime+0x18c
mozjs.dll!JS_SetGCParameterForThread+0x1b78f
mozjs.dll!JS_NewExternalString+0xb6d
mozjs.dll!?StringIsArrayIndex@js@@YA_NPAVJSLinearString@@PAI@Z+0x1dc1
mozjs.dll!JS_SetGCParameterForThread+0x1ec05
mozjs.dll!JS_SetGCParameterForThread+0x1ed6e
Earlier today Firefox just crashed and restarted.
*starts Firefox 15.0.1 again*
Session Manager reports my current session has 840 tabs in 49 windows.
It restored state in just over a minute, which is excellent! Too bad it lost the post i was posting. :(
https://www.mozilla.org/plugincheck/ still uses the vague version string that causes it to always say Flash is outdated:
Shockwave Flash
Shockwave Flash 11.4 r402
However, this time it's right, as http://www.adobe.com/software/flash/about/ says i have 11,4,402,265 installed while 11.4.402.287 is the latest for my system.
*goes to download center to download (and overwrite) installer and installs plugin, IE opens* Must've been the IE version. :/ *tries again, no overwrite needed so assuming this installer is for Firefox* "Close Firefox to continue" *closes Firefox and Continues, IE opens, rates download experience as the worst again* Mozilla's plugincheck shows no difference. Adobe's about screen still says "You have version 11,4,402,265 installed". ... If they weren't incompetent i'd think they're pushing Google Chrome.
Anyway, i'll install that tracer and report back here.
Flags: needinfo?(tmptgr)
Opening the xpi using Firefox 15.0.1 shows me garbled text.
Will the Nightly not break my (work) profile and have an xpi installer?
I've uninstalled Firefox 12, which took Firefox 15 and that maintenance thing with it, and installed Firefox 16. Opening the profiler xpi via File, Open File... got Firefox to recognize it as something it could install, and now i'm running it on a build i'm supposed to use for work.
Nightly and Aurora didn't freeze but lack the Downloads window button, and 16.0.1 still hangs:
mozjs.dll!?PrepareForIncrementalGC@js@@YAXPAUJSRuntime@@@Z+0xe1
mozjs.dll!?GCThingIsMarkedGray@js@@YA_NPAX@Z+0x1d260
mozjs.dll!JS_TraceShapeCycleCollectorChildren+0x12007
mozjs.dll!JS_CallFunctionValue+0x41
xul.dll!NS_CycleCollectorSuspect2_P+0x5d7e
xul.dll!NS_GetXPTCallStub_P+0xca66
xul.dll!NS_NewLocalFile_P+0x38a7
xul.dll!NS_CycleCollectorSuspect2_P+0x3fb3b
xul.dll!?NewObjectOutputWrappedStorageStream@scache@mozilla@@YAIPAPAVnsIObjectOutputStream@@PAPAVnsIStorageStream@@_N@Z+0x326c5
xul.dll!NS_InvokeByIndex_P+0x199
xul.dll!NS_CycleCollectorForget2_P+0x3ead7
xul.dll!NS_CycleCollectorSuspect2_P+0x16d1
xul.dll!NS_CycleCollectorSuspect2_P+0x9f5
xul.dll!NS_CycleCollectorSuspect2_P+0x14cbf
xul.dll!NS_CycleCollectorForget2_P+0x360ad
xul.dll!NS_CycleCollectorSuspect2_P+0x1e2
mozjs.dll!JS_DescribeScriptedCaller+0xa9a
mozjs.dll!??_7DeadObjectProxy@js@@6B@+0xc0
mozjs.dll!JS_DescribeScriptedCaller+0xa9a
mozjs.dll!JS_LookupPropertyWithFlags+0xa417
mozjs.dll!JS_LookupPropertyWithFlags+0x1088a
mozjs.dll!?GCThingIsMarkedGray@js@@YA_NPAX@Z+0x1a3db
xul.dll!JSD_GetScriptFunctionId+0x3d9dd
xul.dll!JSD_GetScriptFunctionId+0x3da6a
mozjs.dll!JS_LookupPropertyWithFlagsById+0xb471
mozjs.dll!?enter@AutoEnterFrameCompartment@JS@@QAE_NPAUJSContext@@PAUJSStackFrame@@@Z+0x542
xul.dll!NS_CycleCollectorSuspect2_P+0xc8a6
mozjs.dll!JS_LookupPropertyWithFlagsById+0x4f6c
mozjs.dll!JS_LookupPropertyWithFlags+0x80a1
mozjs.dll!JS_LookupPropertyWithFlagsById+0x4f6c
mozjs.dll!JS_LookupPropertyWithFlagsById+0x261c
mozjs.dll!?GCThingIsMarkedGray@js@@YA_NPAX@Z+0x19650
xul.dll!JSD_GetScriptFunctionId+0x3d9dd
xul.dll!JSD_GetScriptFunctionId+0x3da6a
mozjs.dll!JS_LookupPropertyWithFlagsById+0xb471
mozjs.dll!?enter@AutoEnterFrameCompartment@JS@@QAE_NPAUJSContext@@PAUJSStackFrame@@@Z+0x542
xul.dll!NS_CycleCollectorSuspect2_P+0xc8a6
mozjs.dll!?PrepareForIncrementalGC@js@@YAXPAUJSRuntime@@@Z+0xe1
mozjs.dll!?GCThingIsMarkedGray@js@@YA_NPAX@Z+0x1d260
mozjs.dll!JS_TraceShapeCycleCollectorChildren+0x12007
mozjs.dll!JS_CallFunctionValue+0x41
xul.dll!NS_CycleCollectorSuspect2_P+0x5d7e
xul.dll!NS_GetXPTCallStub_P+0xca66
xul.dll!NS_NewLocalFile_P+0x38a7
xul.dll!NS_CycleCollectorSuspect2_P+0x3fb3b
xul.dll!?NewObjectOutputWrappedStorageStream@scache@mozilla@@YAIPAPAVnsIObjectOutputStream@@PAPAVnsIStorageStream@@_N@Z+0x326c5
xul.dll!NS_InvokeByIndex_P+0x199
xul.dll!NS_CycleCollectorForget2_P+0x3ead7
xul.dll!NS_CycleCollectorSuspect2_P+0x16d1
xul.dll!NS_CycleCollectorSuspect2_P+0x9f5
xul.dll!NS_CycleCollectorSuspect2_P+0x14cbf
xul.dll!NS_CycleCollectorForget2_P+0x360ad
xul.dll!NS_CycleCollectorSuspect2_P+0x1e2
Here's a new hang in version 17.0.0.4700 with only 5/12 GB RAM used and 10.9 GB free space on C:. Notice the much shorter stacks than those of version 16:
mozjs.dll!JS_GetMethod+0x69a1
mozjs.dll!JS_GetMethod+0x3281
mozjs.dll!JS_SetGCParameterForThread+0x14d49
mozjs.dll!?js_DateGetYear@@YAHPAUJSContext@@PAUJSObject@@@Z+0x363
mozjs.dll!JS_SetGCParameterForThread+0x1c2e1
It just crashed! The details button does nothing, but i pasted this page's URI in the comment field.
According to Process Monitor, the last file activity from Firefox was "C:\Windows\SysWOW64\Macromed\Flash\FlashUtil32_11_5_502_110_ActiveX.exe -Embedding" doing a CreateFile operation on nonexistent "C:\Users\C\telemetry.cfg".
After a little ThreadCreate and ThreadExit activity by IAStorIcon.exe (Intel's Rapid Storage Technology app - i don't know why that even runs as i have only one internal drive), wmiprvse.exe, taskhost.exe, services.exe, hamachi-2.exe, FlashUtil32_11_5_502_110_ActiveX.exe, and lsm.exe, Mozilla's Crash reporter got launched with this command line: "C:\Program Files (x86)\Mozzy Firefox Beta\crashreporter.exe" "C:\Users\C\AppData\Roaming\Mozilla\Firefox\Profiles\un79svfg.default\minidumps\a99d0742-70b0-4538-a1bc-4d302da61999.dmp"
Curiously, even after closing its stack window in Process Explorer, firefox.exe is still running with this unchanging stack:
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x676
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!RtlCreateTagHeap+0xa7
ntdll.dll!LdrInitializeThunk+0xe
USER32.dll!WaitMessage+0x15
xul.dll!NS_CycleCollectorForget2_P+0x2c70b
xul.dll!NS_CycleCollectorSuspect2_P+0x211fb
State is Wait:WrUserRequest. As its start date is only 18 minues ago, this appears to be the restarted Firefox immediately hanging again.
Reporter | ||
Comment 10•12 years ago
|
||
Reporter | ||
Comment 11•12 years ago
|
||
(In reply to Cees T. from comment #10)
> Created attachment 682858 [details]
> Firefox 17 hanging after restart by Mozilla's crash handler
That was probably just Session Manager asking me which 1000+ tab session te restore.
Reporter | ||
Comment 12•12 years ago
|
||
Aurora 2012-11-26 being unresponsive:
ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732
ntoskrnl.exe!KeWaitForMultipleObjects+0xd91
ntoskrnl.exe!KeReleaseSpinLockFromDpcLevel+0x175
xul.dll!JSD_JSDContextForJSContext+0x310a7
xul.dll!XRE_GetProcessType+0x621bb
xul.dll!JSD_JSDContextForJSContext+0x310a4
xul.dll!JSD_ScriptDestroyed+0x33eb6
xul.dll!??4_Init_locks@std@@QAEAAV01@ABV01@@Z+0x59f16
xul.dll!XRE_GetProcessType+0x2340c
xul.dll!XRE_GetProcessType+0x1ab1f
xul.dll!XRE_GetProcessType+0x13695
xul.dll!XRE_GetProcessType+0x136c3
xul.dll!XRE_GetProcessType+0x621e2
ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!__misaligned_access+0xba4
ntoskrnl.exe!__misaligned_access+0x1821
ntoskrnl.exe!__misaligned_access+0x1a97
xul.dll!JSD_JSDContextForJSContext+0x310a7
xul.dll!XRE_GetProcessType+0x621bb
xul.dll!JSD_JSDContextForJSContext+0x310a7
xul.dll!JSD_ScriptDestroyed+0x33eb6
xul.dll!??4_Init_locks@std@@QAEAAV01@ABV01@@Z+0x59f16
xul.dll!XRE_GetProcessType+0x2340c
xul.dll!XRE_GetProcessType+0x1ab1f
xul.dll!XRE_GetProcessType+0x13695
xul.dll!XRE_GetProcessType+0x136c3
xul.dll!XRE_GetProcessType+0x6215c
ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!__misaligned_access+0xba4
ntoskrnl.exe!__misaligned_access+0x1821
ntoskrnl.exe!__misaligned_access+0x1a97
xul.dll!JSD_JSDContextForJSContext+0x310a7
xul.dll!XRE_GetProcessType+0x621bb
xul.dll!JSD_JSDContextForJSContext+0x310a7
xul.dll!JSD_ScriptDestroyed+0x33eb6
xul.dll!??4_Init_locks@std@@QAEAAV01@ABV01@@Z+0x59f16
xul.dll!XRE_GetProcessType+0x2340c
xul.dll!XRE_GetProcessType+0x1ab1f
xul.dll!XRE_GetProcessType+0x13695
xul.dll!XRE_GetProcessType+0x136c3
xul.dll!XRE_GetProcessType+0x621e2
I can't reach the Exit menu option because the Aurora button disappears when i click it and the good old title bar appears instead. *kills Aurora*
Reporter | ||
Comment 13•12 years ago
|
||
Reporter | ||
Comment 14•12 years ago
|
||
Reporter | ||
Comment 15•12 years ago
|
||
Reporter | ||
Comment 16•12 years ago
|
||
Shutting down Eclipse didn't help. Aurora's pane is white as snow. *shoots it*
Reporter | ||
Comment 17•12 years ago
|
||
Aurora being slow to respond to scrolling especially. A while later it spontaneously combusted: https://crash-stats.mozilla.com/report/index/bp-2be68f39-ed49-4e65-9a8f-b22d82121210
Reporter | ||
Comment 18•12 years ago
|
||
Even if i knew how to submit useful info from the Gecko Profiler, Aurora is being too slow to even scroll an old Facebook tab without throwing a fit and blinking its title bar from existence.
Reporter | ||
Comment 19•12 years ago
|
||
I don't know what's going on here, but somehow using 17% of one 2.67 GHz slowed form YuGiOh! BAM on Facebook:
xul.dll!??0_Mutex@std@@QAE@W4_Uninitialized@1@@Z+0xd1033
xul.dll!?PathifyURI@scache@mozilla@@YA?AW4tag_nsresult@@PAVnsIURI@@AAVnsACString_internal@@@Z+0x12bb1
xul.dll!??0_Mutex@std@@QAE@W4_Uninitialized@1@@Z+0xd1033
xul.dll!?SupportImageWithMimeType@imgLoader@@SG_NPBD@Z+0x1663d
xul.dll!?SupportImageWithMimeType@imgLoader@@SG_NPBD@Z+0x163e6
xul.dll!?SupportImageWithMimeType@imgLoader@@SG_NPBD@Z+0x16903
xul.dll!NS_CStringContainerFinish_P+0x39a3
xul.dll!NS_StringContainerInit_P+0x9ae1
xul.dll!XRE_GetProcessType+0x43d45
xul.dll!XRE_GetProcessType+0x16cd8
xul.dll!NS_GetComponentRegistrar_P+0xc44e
xul.dll!XRE_GetProcessType+0x9347f
xul.dll!XRE_GetProcessType+0x92482
xul.dll!XRE_GetProcessType+0x92200
xul.dll!XRE_GetProcessType+0xf8f5
ntdll.dll!RtlIntegerToUnicodeString+0x20b
Aurora 19.0.0.4740. Here is yesterday noon's 10+ MB full profile from Gecko Profiler(?) as recommended in this thread: http://people.mozilla.com/~bgirard/cleopatra/#report=b2cb30b7303f8a2c5734374eac40213e7fda9e7b
Keywords: perf
Looks like a whole array of distinct bugs. They would probably deserve distinct bugzilla entries.
Reporter | ||
Comment 21•12 years ago
|
||
(In reply to David Rajchenbach Teller [:Yoric] <away until Jan 7th> from comment #20)
> Looks like a whole array of distinct bugs. They would probably deserve
> distinct bugzilla entries.
I've narrowed the last laggy issue down to bug 824952, but am not sure how to handle those Process Explorer stacks. Judging by most of my other reports they aren't very useful.
Depends on: 824952
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•