Closed Bug 584551 Opened 11 years ago Closed 11 years ago
Context enters requests in the wrong order
Currently, XPCCallContext::Init enters the request on the new context before pushing it onto the context stack. Pushing a context onto the context stack causes us to set aside the stack chain on it, forcing us to enter a request on it. If the old context was previously in a request, however, this breaks the stack-based discipline that bug 552266 forces on us. In order to avoid this, we need to reverse the order of operations.
Assignee: nobody → mrbkap
Status: NEW → ASSIGNED
Attachment #462987 - Flags: review?(igor)
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [4b3] → [4b3] fixed-in-tracemonkey
Verified that this doesn't crash when I drag tabs to the desktop - for some reason I lost the ability to drop tabs on the desktop for a moment, but it seems to be working now.
You need to log in before you can comment on or make changes to this bug.