Closed Bug 731881 Opened 12 years ago Closed 11 years ago

~nsHttpChannel calls nsXPConnect::GetXPConnect off the main thread via ~XPCTraceableVariant?

Categories

(Core :: Networking: HTTP, defect)

defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: mccr8, Unassigned)

References

Details

(Keywords: crash)

Crash Data

I noticed this crash stack, which is hitting a release assertion that checks that GetXPConnect() isn't called off the main thread.  It looks like nsHttpChannel has some kind of hash table of nsIVariants, and the destructor for an XPCTraceableVariant is trying to grab a lock from XPConnect.

https://crash-stats.mozilla.com/report/index/96622599-ebc5-40bc-b0ae-5daaa2120226

It could be an addon or just the code itself, I don't know.
I only see a single instance of this on 13, and no MOZ_Assert at all in 12, so maybe it is just something weird...
Severity: normal → critical
Depends on: 733235
Keywords: crash
Crash Signature: [@ MOZ_Crash ] → [@ MOZ_Crash ] [@ nsXPConnect::GetXPConnect] [@ nsXPConnect::GetXPConnect()]
I don't see GetXPConnect() in crash stats any more.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
I see a few crashes: https://crash-stats.mozilla.com/report/list?signature=nsXPConnect%3A%3AGetXPConnect%28%29
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Got crash just now: https://crash-stats.mozilla.com/report/index/bp-9264aa21-ebfa-416e-ae26-21eab2121207

Seeing graph of it shows it somehow in high numbers in December 6 build of Nightly.
Sorry for bumping this...
(In reply to Zlip792 from comment #5)
> Got crash just now:
> https://crash-stats.mozilla.com/report/index/bp-9264aa21-ebfa-416e-ae26-
> 21eab2121207
The stack trace is different. It's another issue.
I don't see any crashes like this in the top lists any more.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.