edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: "Kevin Carhart" <kevin_carhart@fastmail.fm>
To: "Karl Dahlke" <eklhad@comcast.net>, edbrowse-dev@edbrowse.org
Subject: [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.
Date: Wed, 18 Nov 2020 09:07:26 -0800	[thread overview]
Message-ID: <34978200-3349-421d-9478-1b336cfcdba1@www.fastmail.com> (raw)
In-Reply-To: <01010175d7b1bc37-735ad9f1-9e72-4fa2-9af5-7743870ada3a-000000@us-west-2.amazonses.com>

[-- 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 --]

           reply	other threads:[~2020-11-18 17:08 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <01010175d7b1bc37-735ad9f1-9e72-4fa2-9af5-7743870ada3a-000000@us-west-2.amazonses.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=34978200-3349-421d-9478-1b336cfcdba1@www.fastmail.com \
    --to=kevin_carhart@fastmail.fm \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=eklhad@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).