Closed
Bug 444880
Opened 16 years ago
Closed 16 years ago
JS component loader needs to use the JS context stack
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
People
(Reporter: bent.mozilla, Assigned: bent.mozilla)
References
Details
Attachments
(1 file, 1 obsolete file)
5.54 KB,
patch
|
bent.mozilla
:
review+
bent.mozilla
:
superreview+
|
Details | Diff | Splinter Review |
JS component loader needs to use the JS context stack. Currently it makes a new request and doesn't suspend any that are on the stack which causes deadlock. Patch attached.
Attachment #329196 -
Flags: superreview?(jst)
Attachment #329196 -
Flags: review?(jst)
Updated•16 years ago
|
Version: unspecified → Trunk
Comment 1•16 years ago
|
||
Comment on attachment 329196 [details] [diff] [review] Patch, v1 - In JSCLContextHelper::~JSCLContextHelper(): + + JSContext* dummy; + mContextStack->Pop(&dummy); It's "ok" to pass null to Pop() here, so no need for the dummy variable. r+sr=jst
Attachment #329196 -
Flags: superreview?(jst)
Attachment #329196 -
Flags: superreview+
Attachment #329196 -
Flags: review?(jst)
Attachment #329196 -
Flags: review+
Assignee | ||
Comment 2•16 years ago
|
||
Removed the dummy var.
Assignee: nobody → bent.mozilla
Attachment #329196 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #330633 -
Flags: superreview+
Attachment #330633 -
Flags: review+
Assignee | ||
Updated•16 years ago
|
Keywords: checkin-needed
Comment 3•16 years ago
|
||
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•16 years ago
|
Keywords: checkin-needed
Comment 4•14 years ago
|
||
This change is now causing a crash when the JS component loader is called from a non-JS thread. Full details posted at: https://bugzilla.mozilla.org/show_bug.cgi?id=419192#c31 Can a check be done, and create a new request (like was being done before this patch) in the situation when there is no existing JS context stack (or whatever the problem is - no js stack for the current thread)?
You need to log in
before you can comment on or make changes to this bug.
Description
•