Closed
Bug 481317
Opened 16 years ago
Closed 16 years ago
ASSERTION: XPConnect is being called on a scope without a 'Components' property! with one tab, ctrl-w
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: Natch, Unassigned)
References
Details
(Keywords: assertion)
file c:/Users/Natch/documents/mozilla_trunk/mozilla-central/js
/src/xpconnect/src/xpcwrappednativescope.cpp, line 764
| Reporter | ||
Updated•16 years ago
|
Summary: ASSERTION: XPConnect is being called on a scope without a 'Components' pr operty! with one tab, ctrl-w → ASSERTION: XPConnect is being called on a scope without a 'Components' property! with one tab, ctrl-w
| Reporter | ||
Comment 1•16 years ago
|
||
Seems like this happens when I exit via [x] as well, but not from the File menu, it doesn't seem to do anything (i.e. no crashes or weird behavior), invalid? or maybe wontfix?
no, these are bugs. the problem is that you have to figure out which JS object isn't listening to enough handlers or, if it seems to be listening to all reasonable handlers, having found the object, determine why the handlers it would listen to aren't being called.
sadly, while it's easy to find who is calling (stack trace), finding out who is being called is painful (i have code in my tree which doesn't work). the easiest thing to do is to log all add's and remove's and then when you get a call check the caller's list of adds+removes and see who hasn't been removed yet.
| Reporter | ||
Comment 3•16 years ago
|
||
Ok, will give a spin, thanks for the tip.
| Reporter | ||
Comment 5•16 years ago
|
||
Not seeing this anymore...
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•