Closed
Bug 586252
Opened 14 years ago
Closed 14 years ago
Assertion failure: !cx->prevRequestContext, at /work/mozilla/builds/2.0.0/mozilla/js/src/jsapi.cpp:779
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bc, Assigned: igor)
References
()
Details
(Keywords: assertion, crash, testcase)
Attachments
(1 file)
(deleted),
text/html
|
Details |
1. http://www.ethiotube.net/video/9849/Breaking-News-Deadly-bomb-blast-at-an-Ethiopian-Restaurant-in-Uganda
2. Assertion failure: !cx->prevRequestContext, at /work/mozilla/builds/2.0.0/mozilla/js/src/jsapi.cpp:779
so far mac os x intel trunk only. more news at 11.
Operating system: Mac OS X
10.5.8 9L34
CPU: x86
GenuineIntel family 6 model 26 stepping 5
1 CPU
Crash reason: EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE
Crash address: 0x0
Thread 0 (crashed)
0 libmozjs.dylib!JS_Assert [jsutil.cpp : 81 + 0x5]
eip = 0x0058029d esp = 0xbfff3100 ebp = 0xbfff3128 ebx = 0x00580254
esi = 0x00b0ad50 edi = 0xbfff3774 eax = 0x00000000 ecx = 0x00000000
edx = 0x00000000 efl = 0x00210246
Found by: given as instruction pointer in context
1 libmozjs.dylib!JS_BeginRequest [jsapi.cpp : 779 + 0x2c]
eip = 0x0042f498 esp = 0xbfff3130 ebp = 0xbfff3158 ebx = 0x0042f379
esi = 0x00b0ad50 edi = 0xbfff3774
Found by: call frame info
2 XUL!JSAutoRequest::JSAutoRequest [jsapi.h : 751 + 0xc]
eip = 0x0513c528 esp = 0xbfff3160 ebp = 0xbfff3178 ebx = 0x04622328
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
3 XUL!XPCJSContextStack::Push [xpcthreadcontext.cpp : 169 + 0x25]
eip = 0x04ea7d4b esp = 0xbfff3180 ebp = 0xbfff31d8 ebx = 0x04622328
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
4 XUL!nsXPConnect::Push [nsXPConnect.cpp : 2689 + 0x1f]
eip = 0x04e6badb esp = 0xbfff31e0 ebp = 0xbfff3218 ebx = 0x04622328
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
5 XUL!nsCxPusher::DoPush [nsContentUtils.cpp : 2973 + 0x18]
eip = 0x046222af esp = 0xbfff3220 ebp = 0xbfff3258 ebx = 0x04622328
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
6 XUL!nsCxPusher::Push [nsContentUtils.cpp : 2956 + 0x11]
eip = 0x046223d9 esp = 0xbfff3260 ebp = 0xbfff3298 ebx = 0x04622328
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
7 XUL!nsCxPusher::Push [nsContentUtils.cpp : 2903 + 0x19]
eip = 0x046225e3 esp = 0xbfff32a0 ebp = 0xbfff32f8 ebx = 0x046223f2
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
8 XUL!nsXBLProtoImplAnonymousMethod::Execute [nsXBLProtoImplMethod.cpp : 321 + 0x11]
eip = 0x0490120e esp = 0xbfff3300 ebp = 0xbfff33a8 ebx = 0x04900f87
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
9 XUL!nsXBLPrototypeBinding::BindingAttached [nsXBLPrototypeBinding.cpp : 486 + 0x17]
eip = 0x048f3a49 esp = 0xbfff33b0 ebp = 0xbfff33d8 ebx = 0x0491257e
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
10 XUL!nsXBLBinding::ExecuteAttachedHandler [nsXBLBinding.cpp : 979 + 0x17]
eip = 0x048edf7c esp = 0xbfff33e0 ebp = 0xbfff3408 ebx = 0x0491257e
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
11 XUL!nsBindingManager::ProcessAttachedQueue [nsBindingManager.cpp : 1019 + 0x12]
eip = 0x04912641 esp = 0xbfff3410 ebp = 0xbfff3458 ebx = 0x0491257e
esi = 0x045011b4 edi = 0xbfff3774
Found by: call frame info
Assignee | ||
Updated•14 years ago
|
Assignee: general → igor
Comment 3•14 years ago
|
||
I'm seeing this crash(?), in this testcase. It's using enhanced privileges, so you need to download it locally to get this crash (?).
Comment 4•14 years ago
|
||
I was writing crash (?), because that's not exactly, what I see in a normal build. There, the browser just hangs, without using any cpu.
Comment 5•14 years ago
|
||
Has this problem gone away now that bug 477999 is fixed? Or did it turn out to have a different cause?
Keywords: testcase
Reporter | ||
Comment 6•14 years ago
|
||
I haven't seen this since the Aug 10-12 timeframe. I'm not clear on the actual dates considering the landings on tracemonkey and the merging to mozilla-central though. I'll assume bug 477999 fixed this though.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•