Closed Bug 571420 Opened 15 years ago Closed 12 years ago

Crash [@ FinalizeArenaList<JSString,&FinalizeString>] during layout/reftests/object/connection-refused.html

Categories

(Core :: JavaScript Engine, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

References

Details

(Keywords: crash, intermittent-failure)

Crash Data

WINNT 5.2 mozilla-central opt test reftest on 2010/06/10 17:36:25 http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1276216585.1276217000.17148.gz&fulltext=1 REFTEST INFO | Loading file:///e:/builds/moz2_slave/mozilla-central-win32-opt-unittest-reftest/build/reftest/tests/layout/reftests/object/connection-refused.html TEST-UNEXPECTED-FAIL | automation.py | Exited with code -1073741819 during test run INFO | automation.py | Application ran for: 0:04:13.907000 INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmpwao22rpidlog ==> process 3552 launched child process 3732 INFO | automation.py | Checking for orphan process with PID: 3732 PROCESS-CRASH | automation.py | application crashed (minidump found) Operating system: Windows NT 5.2.3790 Service Pack 2 CPU: x86 GenuineIntel family 6 model 15 stepping 8 1 CPU Crash reason: EXCEPTION_ACCESS_VIOLATION Crash address: 0x42e3008 Thread 0 (crashed) 0 mozjs.dll!FinalizeArenaList<JSString,&FinalizeString> [jsgc.cpp:ba0db81cc412 : 2494 + 0x0] eip = 0x00427aec esp = 0x00129838 ebp = 0x040fa500 ebx = 0x04000000 esi = 0x042e3000 edi = 0x00059e00 eax = 0x00000001 ecx = 0x00002cf0 edx = 0x02734800 efl = 0x00210246 Found by: given as instruction pointer in context 1 mozjs.dll!GC [jsgc.cpp:ba0db81cc412 : 2866 + 0x5] eip = 0x0049fe7d esp = 0x0012986c ebp = 0x00000000 Found by: call frame info with scanning 2 mozjs.dll!GCUntilDone [jsgc.cpp:ba0db81cc412 : 3156 + 0x5] eip = 0x004a57f6 esp = 0x0012989c ebp = 0x02734800 Found by: call frame info 3 mozjs.dll!js_GC(JSContext *,JSGCInvocationKind) [jsgc.cpp:ba0db81cc412 : 3207 + 0x5] eip = 0x004280d9 esp = 0x001298b4 ebp = 0x00129904 Found by: call frame info 4 mozjs.dll!JS_GC [jsapi.cpp:ba0db81cc412 : 2317 + 0x6] eip = 0x00428024 esp = 0x0012990c ebp = 0x001299d0 Found by: previous frame's frame pointer 5 xul.dll!nsXPConnect::Collect() [nsXPConnect.cpp:ba0db81cc412 : 448 + 0xe] eip = 0x101d1f06 esp = 0x0012991c ebp = 0x001299d0 Found by: call frame info 6 xul.dll!nsCycleCollector::Collect(unsigned int) [nsCycleCollector.cpp:ba0db81cc412 : 2523 + 0x4] eip = 0x101d01f6 esp = 0x001299d8 ebp = 0x0012d884 Found by: previous frame's frame pointer 7 xul.dll!nsCycleCollector_collect() [nsCycleCollector.cpp:ba0db81cc412 : 3220 + 0x10] eip = 0x10219128 esp = 0x0012d88c ebp = 0x0012d900 Found by: previous frame's frame pointer 8 xul.dll!nsJSContext::CC() [nsJSEnvironment.cpp:ba0db81cc412 : 3589 + 0x4] eip = 0x102190f1 esp = 0x0012d898 ebp = 0x0012d900 Found by: call frame info 9 xul.dll!nsJSContext::IntervalCC() [nsJSEnvironment.cpp:ba0db81cc412 : 3677 + 0x4] eip = 0x101d97f6 esp = 0x0012d8a0 ebp = 0x0012d900 Found by: call frame info 10 xul.dll!nsJSContext::CCIfUserInactive() [nsJSEnvironment.cpp:ba0db81cc412 : 3667 + 0x4] eip = 0x105e2163 esp = 0x0012d8b0 ebp = 0x0012d900 Found by: call frame info 11 xul.dll!DocumentViewerImpl::LoadComplete(unsigned int) [nsDocumentViewer.cpp:ba0db81cc412 : 1082 + 0x4] eip = 0x10183dfd esp = 0x0012d8b8 ebp = 0x0012d900 Found by: call frame info 12 xul.dll!nsDocShell::EndPageLoad(nsIWebProgress *,nsIChannel *,unsigned int) [nsDocShell.cpp:ba0db81cc412 : 5756 + 0x16] eip = 0x101921b4 esp = 0x0012d908 ebp = 0x0012da80 Found by: previous frame's frame pointer 13 xul.dll + 0x9d3f03 eip = 0x109d3f04 esp = 0x0012dae4 ebp = 0x0012da80 Found by: call frame info
Crash Signature: [@ FinalizeArenaList<JSString,&FinalizeString>]
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that: * Haven't changed in > 6months * Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb} * Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive. I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases). Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.