973629 - Compartment mismatch in nsXBLBinding::DoInitJSClass

Status: RESOLVED INCOMPLETE

(Core :: XBL, defect)

Description

[Andrew McCreight [:mccr8]]

(In reply to bugzilla.mozilla.org from comment #31)
> Get this "compartment" crash since end of last week (not sure which nightly
> exactly) with an intranet web page that makes heavy use of HTML5 stuff, esp.
> indexedDB and SVG
> 
> https://crash-stats.mozilla.com/report/index/ac51c770-11aa-41cb-9d02-35dda2140217

Can you reproduce this crash in safe mode?  It could be an addon or something.  It would also be good if you could check which Nightly it started failing in.  There are old Nightlies here: ftp://ftp.mozilla.org/pub/firefox/nightly/2014/02/

Bobby, do you know offhand of anything that changed around this last week?

Comment 1

[Bobby Holley (:bholley)]

This is the same as bug 956404 comment 28 and bug 825392 comment 41 right?

Comment 2

[Andrew McCreight [:mccr8]]

Yes, it is probably another symptom of that general problem, though we've hit this same stack before and there were specific fixes (bug 897386, bug 851353) that didn't involve the particular XBL code, whatever that means.

Comment 3

[bugzilla.mozilla.org]

reproducible with a clean profile. But I cannot test anything anymore because I get a lot of other crashes now, clean profile or not

https://crash-stats.mozilla.com/report/index/bp-93a64d5d-d788-4c68-9b87-58e302140218
https://crash-stats.mozilla.com/report/index/bp-c8e8179e-acc3-4335-bee1-821072140218
https://crash-stats.mozilla.com/report/index/bp-2e71ed60-f944-47dc-8989-86b312140218
https://crash-stats.mozilla.com/report/index/bp-04759302-a514-462a-b651-6f51a2140218

But this is apparently a different known bug https://bugzilla.mozilla.org/show_bug.cgi?id=973207

Looking forward to the next nightlies

Comment 4

[Andrew McCreight [:mccr8]]

Can you still reproduce this, now that the other crashes have been fixed?  Thanks.

Comment 5

[Andrew McCreight [:mccr8]]

Can you still reproduce this?  Thanks.

Comment 6

[Bobby Holley (:bholley)]

Whatever was causing this bug, it was probably fixed by bug 825392.

Comment 7

[Andrew McCreight [:mccr8]]

I'm going to close this for now.  Let us know if you are still experiencing this problem.