The default bug view has changed. See this FAQ.

ABORT: Starting new frame but not done with old one!: '!mInFrame'

RESOLVED WORKSFORME

Status

()

Core
ImageLib
--
critical
RESOLVED WORKSFORME
7 years ago
a year ago

People

(Reporter: jdm, Unassigned)

Tracking

({crash})

unspecified
x86_64
Mac OS X
crash
Points:
---

Firefox Tracking Flags

(fennec-)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Created attachment 484943 [details]
Backtrace

Running a recent fennec build, I went to geocities.co.uk, watch the throbber keep spinning indefinitely, brought up the awesomescreen and fennec crashed with the attached backtrace.  Can't reproduce, however.
(Reporter)

Comment 1

7 years ago
I realize that blocking without STR is not likely, but I'd like to get this on the radar.  Chrome process crashes are not fun.
tracking-fennec: --- → ?
2.0 for now, might move up to b3 if it starts showing up in top crashes
tracking-fennec: ? → 2.0+

Comment 3

6 years ago
Are the platform settings on this correct?
(Reporter)

Comment 4

6 years ago
More or less, yes.
Hardware: x86 → x86_64
(In reply to comment #3)
> Are the platform settings on this correct?

(In reply to comment #4)
> More or less, yes.

Ahh... so this is actually OS X only? not blocking then.
tracking-fennec: 2.0+ → 2.0-

Comment 6

6 years ago
fyi, crash automation hit this with a Beta debug build from this morning on xp at http://www.netshoes.com.br/produto/004-9649-028-40?foto=2 but I couldn't reproduce it with local builds from yesterday. I'll rebuild etc and try again.
Blocks: 532972

Updated

6 years ago
Severity: normal → critical

Comment 7

2 years ago
We don't see this in automation anymore.
No longer blocks: 532972
(Reporter)

Comment 8

a year ago
No use keeping this around, in that case.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.