Closed
Bug 856415
Opened 11 years ago
Closed 11 years ago
100% CPU core hang in firefox.exe mozjs.dll!?JS_NewStringCopyN@@YAPAVJSString@@PAUJSContext@@PBDI@Z+0x8c26
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: tmptgr, Unassigned)
Details
(Keywords: hang)
User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E) Steps to reproduce: The same I always do: surf with a 100+ tab session while playing two Flash-based games on Facebook. Recently Aurora crashed a lot, though. Actual results: It stopped responding and is currently hanging and wasting resources. I killed the subprocesses (Real's download plugin probably knocks over the sandbox as well.) but that didn't help. I have ample RAM, CPU cores, and HDD space left, but the fan is annoying at 100%. Have some Process Explorer stack dumps of firefox.exe (21.0.0.4837, 2013-03-30): mozjs.dll!?ToNumberSlow@js@@YA_NPAUJSContext@@VValue@JS@@PAN@Z+0x4151f mozjs.dll!?JS_ValueToId@@YAHPAUJSContext@@VValue@JS@@PAH@Z+0x2377 mozjs.dll!?JS_GetConstructor@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x14e3 mozjs.dll!?JS_WrapPropertyDescriptor@@YAHPAUJSContext@@PAUJSPropertyDescriptor@@@Z+0x124 mozjs.dll!?IncrementalReferenceBarrier@JS@@YAXPAXW4JSGCTraceKind@@@Z+0xde38 mozjs.dll!?JS_ObjectToOuterObject@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x242ca mozjs.dll!?JS_NewStringCopyN@@YAPAVJSString@@PAUJSContext@@PBDI@Z+0x8c26 ntdll.dll!RtlEnterCriticalSection+0x2 nspr4.dll!PR_Lock+0x2e mozjs.dll!?JS_AddNamedValueRootRT@@YAHPAUJSRuntime@@PAVValue@JS@@PBD@Z+0x3046 mozjs.dll!?JS_AddNamedValueRootRT@@YAHPAUJSRuntime@@PAVValue@JS@@PBD@Z+0x2fe7 mozjs.dll!?has@Wrapper@js@@UAE_NPAUJSContext@@PAVJSObject@@HPA_N@Z+0x1264 mozjs.dll!?JS_sprintf_append@@YAPADPADPBDZZ+0x1f9 mozjs.dll!?JS_ValueToId@@YAHPAUJSContext@@VValue@JS@@PAH@Z+0x2377 mozjs.dll!?JS_GetConstructor@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x14e3 mozjs.dll!?JS_WrapPropertyDescriptor@@YAHPAUJSContext@@PAUJSPropertyDescriptor@@@Z+0x124 mozjs.dll!?IncrementalReferenceBarrier@JS@@YAXPAXW4JSGCTraceKind@@@Z+0xde38 mozjs.dll!?JS_ObjectToOuterObject@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x242ca mozjs.dll!?JS_NewStringCopyN@@YAPAVJSString@@PAUJSContext@@PBDI@Z+0x8c26 mozjs.dll!?JS_DestroyContextNoGC@@YAXPAUJSContext@@@Z+0x2200 mozjs.dll!?JS_ValueToId@@YAHPAUJSContext@@VValue@JS@@PAH@Z+0x2377 mozjs.dll!?JS_GetConstructor@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x14e3 mozjs.dll!?JS_WrapPropertyDescriptor@@YAHPAUJSContext@@PAUJSPropertyDescriptor@@@Z+0x124 mozjs.dll!?IncrementalReferenceBarrier@JS@@YAXPAXW4JSGCTraceKind@@@Z+0xde38 mozjs.dll!?JS_ObjectToOuterObject@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x242ca mozjs.dll!?JS_NewStringCopyN@@YAPAVJSString@@PAUJSContext@@PBDI@Z+0x8c26 mozjs.dll!?keys@Wrapper@js@@UAE_NPAUJSContext@@PAVJSObject@@AAVAutoIdVector@JS@@@Z+0x2f66 mozjs.dll!?JS_ValueToId@@YAHPAUJSContext@@VValue@JS@@PAH@Z+0x2377 mozjs.dll!?JS_GetConstructor@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x14e3 mozjs.dll!?JS_WrapPropertyDescriptor@@YAHPAUJSContext@@PAUJSPropertyDescriptor@@@Z+0x124 mozjs.dll!?IncrementalReferenceBarrier@JS@@YAXPAXW4JSGCTraceKind@@@Z+0xde38 mozjs.dll!?JS_ObjectToOuterObject@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x242ca mozjs.dll!?JS_NewStringCopyN@@YAPAVJSString@@PAUJSContext@@PBDI@Z+0x8c26 mozjs.dll!?JS_SetElement@@YAHPAUJSContext@@PAVJSObject@@IPAVValue@JS@@@Z+0xbf9 mozjs.dll!?JS_malloc@@YAPAXPAUJSContext@@I@Z+0x1b31 mozjs.dll!?JS_ValueToId@@YAHPAUJSContext@@VValue@JS@@PAH@Z+0x2377 mozjs.dll!?JS_GetConstructor@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x14e3 mozjs.dll!?JS_WrapPropertyDescriptor@@YAHPAUJSContext@@PAUJSPropertyDescriptor@@@Z+0x124 mozjs.dll!?IncrementalReferenceBarrier@JS@@YAXPAXW4JSGCTraceKind@@@Z+0xde38 mozjs.dll!?JS_ObjectToOuterObject@@YAPAVJSObject@@PAUJSContext@@PAV1@@Z+0x242ca mozjs.dll!?JS_NewStringCopyN@@YAPAVJSString@@PAUJSContext@@PBDI@Z+0x8c26 Expected results: Fail gracefully instead of going into an infinite/slow loop that kills responsiveness.
Component: General → JavaScript Engine
Summary: 100% CPU core hang in firefox.exe → 100% CPU core hang in firefox.exe mozjs.dll!?JS_NewStringCopyN@@YAPAVJSString@@PAUJSContext@@PBDI@Z+0x8c26
Comment 1•11 years ago
|
||
Could you be more specific as to which games you're playing?
Flags: needinfo?(tmptgr)
Resolving this incomplete since it's been over a month without actionable information added to this bug report. Cees, please reopen this bug if you can still reproduce on the latest Nightly build and please provide more detailed steps to reproduce (including URLs).
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Currently https://apps.facebook.com/pockie-ninja-ii/?fb_source=appcenter&fb_appcenter=1#_=_ only crashes Flash, and https://apps.facebook.com/stormfall/?fb_source=canvasbookmark&count=0 had some z-order issues. I haven't played https://apps.facebook.com/yugioh-bam/?fb_source=canvasbookmark&count=0 in a while, but last time i did the animations were choppy.
Flags: needinfo?(tmptgr)
You need to log in
before you can comment on or make changes to this bug.
Description
•