Closed Bug 307247 Opened 19 years ago Closed 11 years ago

ASSERTION: JSContext still in threadjscontextstack!: '!tls->GetJSContextStack() || !tls->GetJSContextStack()-> DEBUG_StackHasJSContext(aJSContext)' @

Categories

(Core :: XPConnect, defect)

1.8 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bc, Unassigned)

References

()

Details

(Keywords: assertion, qawanted, top100)

Attachments

(1 file)

Found this with a CVS Firefox 1.5 build from 2005-09-05, cancel the auth dialog to get the assert. Related to bug 294431? ###!!! ASSERTION: JSContext still in threadjscontextstack!: '!tls->GetJSContextStack() || !tls->GetJSContextStack()-> DEBUG_StackHasJSContext(aJSContext)', file c:/work/mozilla/builds/ff/1.5/mozilla/js/src/xpconnect/src/nsXPConnect.cpp, line 1158 nsXPConnect::ReleaseJSContext(nsXPConnect * const 0x00ed1588, JSContext * 0x0349b4f8, int 0) line 1158 nsJSContext::~nsJSContext() line 742 nsJSContext::`scalar deleting destructor'(unsigned int 1) + 15 bytes nsJSContext::Release(nsJSContext * const 0x0349b350) line 770 + 215 bytes nsTimerImpl::ReleaseCallback() line 117 + 18 bytes nsTimerImpl::~nsTimerImpl() line 166 nsTimerImpl::`scalar deleting destructor'(unsigned int 1) + 15 bytes nsTimerImpl::Release(nsTimerImpl * const 0x034afd50) line 98 + 28 bytes nsTimerManager::FireNextIdleTimer(nsTimerManager * const 0x00f830e0) line 628 + 12 bytes nsAppShell::Run(nsAppShell * const 0x00f515f8) line 142 nsAppStartup::Run(nsAppStartup * const 0x00f51558) line 145 + 26 bytes XRE_main(int 3, char * * 0x003f6f60, const nsXREAppData * 0x0042201c kAppData) line 2322 + 35 bytes main(int 3, char * * 0x003f6f60) line 61 + 18 bytes mainCRTStartup() line 338 + 17 bytes KERNEL32! 7c816d4f()
(In reply to comment #0) This stack is probably entirely bogus. I will try to get a good one later today.
Summary: ###!!! ASSERTION: JSContext still in threadjscontextstack!: '!tls->GetJSContextStack() || !tls->GetJSContextStack()-> DEBUG_StackHasJSContext(aJSContext)' @ → ASSERTION: JSContext still in threadjscontextstack!: '!tls->GetJSContextStack() || !tls->GetJSContextStack()-> DEBUG_StackHasJSContext(aJSContext)' @
i'm ambivalent as to whether this is more appropriate here or in my bug. ###!!! WARNING: event queue chain length is 6. this is almost certainly a leak., file r:/mozilla/xpcom/threads/nsEventQueue.cpp, line 555 ++DOMWINDOW == 32 vnk: Application venkman, 'JavaScript Debugger' unloading. ###!!! ASSERTION: JSContext still in threadjscontextstack!: '!tls->GetJSContextStack() || !tls->GetJSContextStack()-> DEBUG_StackHasJSContext(aJSContext)', file r:/mozilla/js/src/xpconnect/src/nsXPConnect.cpp, line 1194 Break: at file r:/mozilla/js/src/xpconnect/src/nsXPConnect.cpp, line 1194 The problem i had in this session was that windows i opened w/ window.open() never appeared (and really never finished, and hence was still in the event queue chain). so i asked venkman to close them using window.close(), which it mostly did (except things were still in the event queue chain...).
Assignee: dbradley → nobody
QA Contact: pschwartau → xpconnect
Is this bug (or bug 294431) reproducible in recent trunk/branch builds?
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: