Closed Bug 502730 Opened 11 years ago Closed 11 years ago
ASSERTION: Wrong scope, this is really bad!: 'JS
_Get Global For Object(cx, obj) == new Scope'
build id: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090706 Minefield/3.6a1pre ID:20090706143743 Use the following in-line JS into the location bar on a debug build of trunk document.write("<head></head><body></body>"); This is referenced off of bug 465752 and the JS listed there by bz
I can reproduce. ###!!! ASSERTION: Wrong scope, this is really bad!: 'JS_GetGlobalForObject(cx, obj) == newScope', file /Users/jruderman/central/content/base/src/nsDocument.cpp, line 3566
Peter, Blake, this looks related to stuff you've looked into recently... and which might want on branches. It would be really nice to have a regression range here to make sure we _don't_ land this on branch all-unknowing.
Peter, could you have a look at this one? I think it'd be good to at least understand more about this for 1.9.2...
Assignee: nobody → peterv
Flags: blocking1.9.2? → blocking1.9.2+
Priority: -- → P2
Hmm, we check the scope before OpenCommon reparents the wrapper. We somehow need to relax this assertion in that case.
The assertion was added in bug 499910, so pretty sure that's where the regression comes from.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.2a1
This is a debug only patch, removing a false-positive occurrence of an assertion. The assertion is pretty important, so I think it'd be good to resolve this on the branch too so we avoid confusion (see bug 517711).
Attachment #422532 - Flags: approval18.104.22.168?
Comment on attachment 422532 [details] [diff] [review] v1 (1.9.1 branch version) Approved for 22.214.171.124, a=dveditz for release-drivers
Attachment #422532 - Flags: approval126.96.36.199? → approval188.8.131.52+
peterv: please land this today if it's going to make 184.108.40.206, otherwise it'll have to go into a future release.
Attachment #422532 - Flags: approval220.127.116.11+ → approval18.104.22.168?
Comment on attachment 422532 [details] [diff] [review] v1 (1.9.1 branch version) next release it is: approval22.214.171.124 removed.
Comment on attachment 422532 [details] [diff] [review] v1 (1.9.1 branch version) I shouldn't have moved the request from 126.96.36.199 to 188.8.131.52 -- it's possible it missed 184.108.40.206 because you don't really want it anymore. Please re-request approval if you do still want this on the 1.9.1 branch
Guess we're wontfixing this for the 1.9.1 branch
You need to log in before you can comment on or make changes to this bug.