Last Comment Bug 681071 - Lower the boom on cross-compartment pointers
: Lower the boom on cross-compartment pointers
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Trunk
: All All
: -- normal (vote)
: mozilla9
Assigned To: Bill McCloskey (:billm)
:
Mentors:
Depends on:
Blocks: 670702
  Show dependency treegraph
 
Reported: 2011-08-22 14:45 PDT by Bill McCloskey (:billm)
Modified: 2011-08-25 18:34 PDT (History)
6 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
patch (5.60 KB, patch)
2011-08-22 14:45 PDT, Bill McCloskey (:billm)
dmandelin: review+
Details | Diff | Review

Description Bill McCloskey (:billm) 2011-08-22 14:45:44 PDT
Created attachment 554971 [details] [diff] [review]
patch

There's evidence in bug 670702 that we still have problems with pointers that cross into other compartments without the right wrappers. Right now we check for this during Mark. This patch adds new assertions so that hopefully we can catch these problems right away. These checks will be expensive so I'll probably back them out after a week. They shouldn't affect our benchmarking of development builds because they'll only be enabled in actual nightly builds.

I also found a stupid bug in my instrumentation that caused some asserts and poisoning to be disabled in debug builds. This fixes that.
Comment 1 David Mandelin [:dmandelin] 2011-08-22 18:28:23 PDT
Comment on attachment 554971 [details] [diff] [review]
patch

Review of attachment 554971 [details] [diff] [review]:
-----------------------------------------------------------------

Just be sure to coordinate with TI landing if this might affect that.
Comment 2 Bill McCloskey (:billm) 2011-08-25 10:10:28 PDT
I checked with Brian; he says it shouldn't be a problem.
Comment 3 Ed Morley [:emorley] 2011-08-25 18:34:29 PDT
http://hg.mozilla.org/mozilla-central/rev/d4003f345b24

Note You need to log in before you can comment on or make changes to this bug.