Closed
Bug 1281126
Opened 9 years ago
Closed 9 years ago
Crash in eme-adobe.dll@0x3ec3f4 mostly on AuthenticAMD family 15 model 107 stepping 1 | 2
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| platform-rel | --- | - |
People
(Reporter: cpearce, Unassigned)
Details
(Keywords: crash, Whiteboard: [platform-rel-AMD])
Crash Data
This bug was filed from the Socorro interface and is
report bp-1e1465c6-24c1-4383-ad33-dd2f92160616.
=============================================================
Someone added an info bar to prompt users to submit unreported crash reports.
I expect this is the crash we experienced using the Adobe GMP for unencrypted decoding.
These are mostly on "AuthenticAMD family 15 model 107 stepping 1 | 2" and similar.
P2 because unencrypted decoding is disabled for now.
Priority: -- → P2
| Reporter | ||
Comment 2•9 years ago
|
||
Adding Joe Steele, from Adobe.
Debugging the minidump for this crash report:
https://crash-stats.mozilla.com/report/index/654a3d58-633d-411a-b94f-1a5fa2160623#allthreads
If I follow the breadcrumbs through the minidump, I can see that the Adobe DLL has thrown a Microsoft C++, "bad_alloc" C++ exception.
Joe, do you get anything from the thread call stacks listed in the above link? There's probably a new[] that's getting an invalid or too large size passed to it that's failing.
Flags: needinfo?(steele)
Comment 3•9 years ago
|
||
I will see if I can re-symbolize the call stack. Unless you have some reason to suspect low memory, I would guess this is a memory stomper of some kind leading to try and alloc an unrealistic memory size.
Mass change P2 -> P3
Priority: P2 → P3
Updated•9 years ago
|
platform-rel: --- → ?
Whiteboard: [platform-rel-AMD]
Updated•9 years ago
|
platform-rel: ? → -
| Reporter | ||
Comment 5•9 years ago
|
||
We're removing Adobe EME support, so closing this bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
| Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(steele)
You need to log in
before you can comment on or make changes to this bug.
Description
•