Closed Bug 5735 Opened 26 years ago Closed 26 years ago

[xpc] no way to eliminate JSContexts from the context map

Categories

(Core :: XPCOM, defect, P3)

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: waterson, Assigned: jband_mozilla)

References

Details

nsXPConnect::InitJSContext() is failing because it finds the JSContext in its map. I talked with jband about this, and he believes that the problem has to do with a recycled pointer. Said we needed to implement a method for telling xpconnect that a JSContext is getting tossed, so that he can unmap it.
adding myself to cc: list as this bug manifests itself in mail usage, causing crashes. See dup bug 5719
Status: NEW → ASSIGNED
I'm about to mark 5719 as a dup of this bug but we have 5719 as a M6 stopper bug because it crashes mail after displaying several messages in a row. Can we set the fix for this as M6 as well?
*** Bug 5719 has been marked as a duplicate of this bug. ***
Pls change the severity of this bug to "major" or "critical" since a side effect is a crash on mail.
I have fixes for this in my tree. This required a bunch of small changes to xpconnect internals. I can't promise that there won't be new instabilities without really exercizing it in the browser. Do we want this to go into M6 or not?
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Component: xpidl → XPCOM
QA Contact: mike+mozilla → xpcom
You need to log in before you can comment on or make changes to this bug.