[edbrowse-dev] Re: [Bug 1676615] In mozjs-60, we create a class in one compartment, instantiate it in another, and get a seg fault at DestroyContext.

[edbrowse-dev] Re: [Bug 1676615] In mozjs-60, we create a class in one compartment, instantiate it in another, and get a seg fault at DestroyContext.

[Kevin Carhart]

[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]

We got attention from Jason Orendorff at Mozilla:



On Tue, Nov 17, 2020, at 11:32 AM, Bugzilla@Mozilla wrote:
> Do not reply to this email. You can add comments to this bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1676615
> 
> *Jason Orendorff [:jorendorff] <mailto:jorendorff@mozilla.com> changed Bug 1676615 <https://bugzilla.mozilla.org/show_bug.cgi?id=1676615> at 2020-11-17 11:32:23 PST*:
> 
> 
> *What*
> *Removed*
> *Added*
> CC
>  
> jorendorff@mozilla.com
> Closed
>  
> 2020-11-17 19:32:23
> Resolution
> ---
> INVALID
> Status
> UNCONFIRMED
> RESOLVED
> 
> *Comment # 1 <https://bugzilla.mozilla.org/show_bug.cgi?id=1676615#c1> on Bug 1676615 <https://bugzilla.mozilla.org/show_bug.cgi?id=1676615> from Jason Orendorff [:jorendorff] <mailto:jorendorff@mozilla.com> at 2020-11-17 11:32:23 PST * 
> This has always been invalid use of the API. `JS_DefineProperty(cx, g2, "link", v, 0);` requires that cx, g2, and v be same-compartment. Here the value `v` is `g1`, a global in a different compartment.

> The rule is enforced with assertions in debug builds—we strongly recommend using a debug build for development, as there are many assertions that check API usage, and the API is very error-prone without those checks.

> Marking this as RESOLVED INVALID which just means it looks like there is not a bug to fix.

> 
> Product/Component: Core :: JavaScript Engine
> *You are receiving this mail because:* 
>  * You are on the CC list for the bug.
>  * You reported the bug.
> Configure your email settings at https://bugzilla.mozilla.org/userprefs.cgi?tab=email.
> 

[-- Attachment #2: Type: text/html, Size: 6226 bytes --]