Closed Bug 1132195 Opened 9 years ago Closed 9 years ago

Crash [@ nsXPConnect::XPConnect() ]

Categories

(Core :: Graphics: ImageLib, defect)

Product:
Core
Component:
Graphics: ImageLib
Platform:
x86
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: johnp, Unassigned)

References

Details

(Keywords: crash)

Crash Data

I've started experiencing this crash immediately after updating Nightly and it reproduces for me with a lot of websites, the first I tried multiple times was noscript.net because of the stack showing a comment about extensions and after checking which were updated today (DTA Nightly and Noscript latest RC), I wanted to check the respective changelog.

I'm gonna try reproducing this without NoScript...
Crash Signature: [@ nsXPConnect::XPConnect() ]
Keywords: crash
Ok, with NoScript I crashed with 

bp-339fb038-0469-406b-90f6-fa85b2150211

without I crash a couple seconds later with bug 1116067.
Just checked that bug, and it's a different stack trace. Mine is:

bp-e242f3e2-30de-42c9-9bda-e0d212150211
Crash Signature: [@ nsXPConnect::XPConnect() ] → [@ nsXPConnect::XPConnect() ] [@ NS_CycleCollectorSuspect3 ]
Ohhh dear. We're doing image loading off the main thread and there's a JS web progress listener that gets triggered. That's fun. I'm not really sure where this belongs, so I'm CCing people who are familiar with these things.
Johannes, could you file a separate bug in Core :: Imagelib for your non-NoScript stack trace? It's different than bug 1116067 and should be triaged separately.
Flags: needinfo?(johnp)
Done. Bug 1132199 and you're cc'ed to it.
Crash Signature: [@ nsXPConnect::XPConnect() ] [@ NS_CycleCollectorSuspect3 ] → [@ nsXPConnect::XPConnect() ]
Flags: needinfo?(johnp)
http://forums.mozillazine.org/viewtopic.php?f=23&t=2912993

More crashes with different stats

Maybe it help.
This is already fixed, but it looks like it just _barely_ missed the latest Nightly. See bug 1130707 comment 7.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Any chance in a respin this late?
Component: General → ImageLib
(In reply to Johannes Pfrang [:johnp] from comment #9)
> Any chance in a respin this late?

Do we do respins for Nightly? It will definitely be in the next Nightly release that'll be baked tonight; I'm not sure it's worth trying to get it out less than 12 hours earlier.
Actually, I changed my mind here! I've received several more comments about this in the last few minutes, so it seems to be pretty widespread. Also, apparently I was wrong about us not doing Nightly respins.

So: I'm going to try to get a respin done. Will report back.
OK, KWierso triggered a respin. So an updated version of Nightly is on its way ASAP.
You need to log in before you can comment on or make changes to this bug.