Closed Bug 545333 Opened 14 years ago Closed 14 years ago

Intermittent tjss crash [@ 0x2f49204d] [@ JS_TraceChildren] loading real-base64-4.html

Categories

(Core :: JavaScript Engine, defect)

x86
Windows Vista
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1265780120.1265780657.26763.gz
WINNT 6.0 mozilla-central talos jss on 2010/02/09 21:35:20  
s: talos-rev2-vista07

NOISE: Cycle 1: loaded http://localhost/page_load_test/jss/real-base64-3.html (next: http://localhost/page_load_test/jss/real-base64-4.html)
NOISE: 
NOISE: __FAILbrowser non-zero return code (-1073741819)__FAIL
NOISE: Found crashdump: c:\users\mozqa\appdata\local\temp\tmp8je0nq\profile\minidumps\84a03931-c78a-4a6e-9624-7ad6ba92b99e.dmp
Operating system: Windows NT
                  6.0.6000 
CPU: x86
     GenuineIntel family 6 model 15 stepping 2
     2 CPUs

Crash reason:  EXCEPTION_ACCESS_VIOLATION
Crash address: 0x2f49204d

Thread 0 (crashed)
 0  0x2f49204d
    eip = 0x2f49204d   esp = 0x0025cd7c   ebp = 0x00000100   ebx = 0x0025ce20
    esi = 0x00822600   edi = 0x0080d800   eax = 0x2f49204d   ecx = 0x0025ce20
    edx = 0x6cb41690   efl = 0x00010283
    Found by: given as instruction pointer in context
 1  mozjs.dll!JS_TraceChildren [jsgc.cpp:b2e6a7183e28 : 1865 + 0x6]
    eip = 0x6d723208   esp = 0x0025cd80   ebp = 0x00000100
    Found by: stack scanning
 2  mozjs.dll!JS_CallTracer [jsgc.cpp:b2e6a7183e28 : 2141 + 0xb]
    eip = 0x6d723895   esp = 0x0025cd8c   ebp = 0x00000100
    Found by: call frame info with scanning
 3  mozjs.dll!js_TraceContext + 0x201
    eip = 0x6d790edb   esp = 0x0025cdac   ebp = 0x0025d28c
    Found by: call frame info with scanning
 4  0x0
    eip = 0x00000001   esp = 0x0025d294   ebp = 0x0025d264
    Found by: previous frame's frame pointer
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Also it occurs on Linux
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.