Closed
Bug 650275
Opened 14 years ago
Closed 14 years ago
"ABORT: bad scope for new JSObjects" with setTimeout
Categories
(Core :: Security, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox5 | - | wontfix |
firefox6 | + | fixed |
blocking2.0 | --- | - |
status2.0 | --- | wanted |
status1.9.2 | --- | unaffected |
blocking-fx | --- | ? |
status1.9.1 | --- | unaffected |
People
(Reporter: moz_bug_r_a4, Assigned: mrbkap)
References
Details
(Whiteboard: [sg:critical?] fixed-in-tracemonkey)
Attachments
(1 file)
553 bytes,
text/html
|
Details |
###!!! ABORT: bad scope for new JSObjects: 'type.IsArithmetic() || cx->compartment == lccx.GetScopeForNewJSObjects()->compartment()', file js/src/xpconnect/src/xpcconvert.cpp, line 253
![]() |
||
Updated•14 years ago
|
Comment 1•14 years ago
|
||
Doesn't look like a chemspill bug and we're not planning any more 4.0.x releases.
Comment 2•14 years ago
|
||
Is this something we should be tracking for FF5? We are skipping these in the Aurora triage meetings and deferring the decision to the crit smash team. Can someone make a call on +/- here?
Comment 3•14 years ago
|
||
Tracking this for 5. Blake has a fix in the works.
No longer depends on: 650273
Comment 4•14 years ago
|
||
Blake, do you have a status? When do we expect a fix to be ready?
Updated•14 years ago
|
status1.9.1:
--- → unaffected
status1.9.2:
--- → unaffected
Assignee | ||
Comment 5•14 years ago
|
||
I have a patch that works but breaks a mochitest. I'm not sure how important the test is, though. I'll try to figure it out tomorrow.
Comment 6•14 years ago
|
||
We're now quite late in the game for Firefox 5. Does the fix at bug 650273 remedy this?
Assignee | ||
Comment 7•14 years ago
|
||
Yes, it does.
Whiteboard: [sg:critical?] → [sg:critical?] fixed-in-tracemonkey
Comment 8•14 years ago
|
||
bug 650273 is fixed on mozilla-central
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 9•14 years ago
|
||
Per discussion with mrbkap and dveditz we've decided that it's too late to fix this for 5, but it's already fixed for 6.
Updated•13 years ago
|
Group: core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•