crash in GLEngine@0xaa... with Flash

RESOLVED FIXED in Firefox 15



5 years ago
5 years ago


(Reporter: mccr8, Unassigned)


(Blocks: 1 bug, 4 keywords)

15 Branch
Mac OS X
crash, regression, reproducible, topcrash

Firefox Tracking Flags

(firefox15+ fixed)


(Whiteboard: [qa-], crash signature)



5 years ago
This bug was filed from the Socorro interface and is 
report bp-5b576f82-7fd6-4fd0-8821-d06492120509 .
In Google Reader, I am subscribed to the "Official Gmail Blog".  Twice now, when I've clicked on the link to bring up the entries for the blog, then clicked on the latest entry, it has crashed immediately with this signature.

Comment 1

5 years ago
I get similar crashes when I load the Amazon Cloud player:

Comment 2

5 years ago
I used the Amazon Cloud player yesterday, so this is probably a very recent regression.
Andrew: I tried to repro on Amazon Cloud player and with Google Reader using Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/15.0 Firefox/15.0a1 but so far I have not luck reproducing. Wondering if maybe an extension is tickling the crash?
Crash Signature: [@ GLEngine@0xaa5ba] → [@ GLEngine@0xaa5ba] [@ GLEngine@0xaaf9d]

Comment 4

5 years ago
Yeah, it turns out I can't reproduce on a clean profile either.  I'll try figuring out if it is an addon.

Comment 5

5 years ago
I still get it without any extensions, in my main profile.  I tried enabling/disabling incremental GC but it didn't seem to matter.  If I disable Flash, then it loads up without crashing, but of course it doesn't actually play anything.

Comment 6

5 years ago
I have Flash, which is apparently out of date.  I'll try upgrading it.

Comment 7

5 years ago
Both that Google Reader entry and the Amazon Cloud player work just fine with Flash, so maybe this was some kind of Flash bug.


5 years ago
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME


5 years ago
Summary: crash in GLEngine@0xaa5ba → crash in GLEngine@0xaa5ba with Flash
Adding Sal from Adobe - would be interesting to know why that flash version is crashing in this instance. I was running with the latest version Version: and that was likely why I was not able to reproduce the crash.

Comment 9

5 years ago
I couldn't reproduce on a clean profile even with 233, so maybe my profile was just mangled in some odd way.

Comment 10

5 years ago
i'm glad it's working for you on a clean profile.  11,2,202,235 was a security update only.

Comment 11

5 years ago
It's hit by many users and is currently #3 top crasher in today's build.
The regression range is:
It might be a regression from bug 749678.

More reports at:
tracking-firefox15: --- → ?
Keywords: regression, reproducible, topcrash
Hardware: All → x86_64
Resolution: WORKSFORME → ---
Summary: crash in GLEngine@0xaa5ba with Flash → crash in GLEngine@0xaa... with Flash
Version: Trunk → 15 Branch
Crash Signature: [@ GLEngine@0xaa5ba] [@ GLEngine@0xaaf9d] → [@ GLEngine@0xaa5ba] [@ GLEngine@0xaaf9d] [@ GLEngine@0xae365]
Crash Signature: [@ GLEngine@0xaa5ba] [@ GLEngine@0xaaf9d] [@ GLEngine@0xae365] → [@ GLEngine@0xaa5ba] [@ GLEngine@0xaaf9d] [@ GLEngine@0xae365] [@ GLEngine@0x4230d]
I can reproduce this consistently in my daily profile by visiting and clicking on the "teaser reel" link.
I can also reproduce it consistently by opening in a new tab.
Indeed, there is clearly a regression with plugins using OpenGL, which means in particular Flash on Mac OSX, from bug 749678.

I just backed it out on inbound:

With this commit message:

Unfortunately, in-process plugins using OpenGL break the assumption made by these patches, that the current GL context is only changed by GLContext::MakeCurrent. Another issue, regardless of in-process, is that our host-side code in uses direct CGL calls, bypassing GLContext.


5 years ago
Blocks: 749678


5 years ago
tracking-firefox15: ? → +

Comment 15

5 years ago
There are no crashes after 15.0a1/20120513. It's fixed by the backout of bug 749678.
Last Resolved: 5 years ago5 years ago
status-firefox15: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla15


5 years ago
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.