Closed Bug 1200085 Opened 9 years ago Closed 9 years ago

Firefox 40.0.2 Crash [@ libgmpopenh264.dylib@0x25c1 ]

Categories

(Core :: WebRTC: Audio/Video, defect, P1)

Product:
Core
Component:
WebRTC: Audio/Video
Version:
40 Branch
Platform:
x86
macOS
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: ruil2, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Keywords: crash)

Crash Data

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/600.6.3 (KHTML, like Gecko) Version/8.0.6 Safari/600.6.3 Steps to reproduce: This crash happened after start,stop video several times crash link: https://crash-stats.mozilla.com/report/index/f4648e5e-a469-499c-a3f3-8186b2150826
can't reproduce this issue on trunk
Crash Signature: [@ libgmpopenh264.dylib@0x25c1]
Blocks: WebRTC-OpenH264
URL: https://crash-stats.mozilla.com/repor...
Severity: normal → critical
Component: Untriaged → WebRTC: Audio/Video
Keywords: crash
OS: Unspecified → Mac OS X
Product: Firefox → Core
Hardware: Unspecified → x86
Ethan -- Is this likely a dup of the GMP ref counting bug?
backlog: --- → webrtc/webaudio+
Rank: 15
Flags: needinfo?(ethanhugg)
Priority: -- → P1
Yes, because as Karina noted, it happens on v1.4 but not on the master branch where the refcounting has been added.
Flags: needinfo?(ethanhugg)
Resolving; will be fixed by 1.5 update of OpenH264
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Apparently this is not fixed with the 1.5 release: https://crash-stats.mozilla.com/report/index/46dcca2f-3e23-44d8-806a-9dd472151111 Only encountered it once. So it is probably hard to reproduce.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INCOMPLETE → ---
Note: the crash address in the plugin has changed in the 1.5 plugin, but the stack looks the same to me. Because of the same stack I assume this the same bug.
This stack is the same crash we're fixing 1.5.1, so this should be addressed with the 1.5.1 spin Callek is doing now.
Fixed by v1.5.1.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Depends on: 1217114
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.