Closed Bug 546764 Opened 14 years ago Closed 14 years ago

Crash [@JS_CallTracer ] when running test_HTMLOptionsCollection06.html

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking2.0 --- beta1+

People

(Reporter: sdwilsh, Unassigned)

References

Details

(Keywords: intermittent-failure) 

WINNT 5.2 mozilla-central opt test mochitests-3/5 on 2010/02/17 14:05:47  

3146 INFO Running /tests/dom/tests/mochitest/dom-level2-html/test_HTMLOptionsCollection06.html...
TEST-UNEXPECTED-FAIL | automation.py | Exited with code -1073741819 during test run
INFO | automation.py | Application ran for: 0:02:04.047000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmp3go1wkpidlog
==> process 924 launched child process 4036
INFO | automation.py | Checking for orphan process with PID: 4036
PROCESS-CRASH | automation.py | application crashed (minidump found)
Operating system: Windows NT
                  5.2.3790 Service Pack 2
CPU: x86
     GenuineIntel family 6 model 23 stepping 8
     1 CPU

Crash reason:  EXCEPTION_ACCESS_VIOLATION
Crash address: 0xfc0

Thread 0 (crashed)
 0  mozjs.dll!JS_CallTracer [jsgc.cpp:1b944ebb5ca6 : 2112 + 0x28]
    eip = 0x6024e2d8   esp = 0x0012cea4   ebp = 0x09266000   ebx = 0x0012cf28
    esi = 0x00000002   edi = 0x00000008   eax = 0x00000fc0   ecx = 0x00000001
    edx = 0x00000000   efl = 0x00210246
    Found by: given as instruction pointer in context
 1  mozjs.dll!js_TraceContext + 0x201
    eip = 0x60280f54   esp = 0x0012ceb4   ebp = 0x0012d4cc
    Found by: call frame info with scanning
 2  0x0
    eip = 0x00000001   esp = 0x0012d4d4   ebp = 0x0012d4a4
    Found by: previous frame's frame pointer
blocking2.0: --- → ?
I don't think this has happened again.
Status: NEW → RESOLVED
blocking2.0: ? → beta1+
Closed: 14 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.