Closed Bug 1370015 Opened 7 years ago Closed 7 years ago

Crash in nsFrameLoader::~nsFrameLoader

Categories

(Core :: DOM: Content Processes, defect)

Unspecified
Windows 10
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: MatsPalmgren_bugz, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-a9520783-6691-4f8c-b8a1-f5c8e0170603.
=============================================================

This signature is spiking in Nightly starting in build 20170531030204.
It's a release assert added in bug 1126089 causing it:
MOZ_CRASH Reason:  MOZ_RELEASE_ASSERT(mDestroyCalled)
Oh, I noted just now that bug 1126089 is from two years ago some it
must be something else that's causing these crashes now.
It's also worth noting that there are no crashes *after* 20170531030204,
so perhaps these were caused by something bad that got backed out?

Let's watch this for a few days and then resolve as WFM unless we get
crashes in newer builds...
No longer blocks: 1126089
Severity: critical → normal
All recent reported crashes are in 20170531030204, so I think the issue
has been resolved in fixed builds.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
So I think the issue has been fixed in later builds, is what I meant to say.
You need to log in before you can comment on or make changes to this bug.