Closed Bug 1339918 Opened 7 years ago Closed 7 years ago

Crash in mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::gmp::PGMPDecryptorChild::OnMessageReceived

Categories

(Core :: Audio/Video: GMP, defect, P2)

Unspecified
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox54 --- affected

People

(Reporter: dholbert, Unassigned)

References

()

Details

(Keywords: crash, stale-bug)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-9419677f-3b21-4182-bcb0-1e1fa2170215.
=============================================================
In my Firefox Nightly browsing session right now: every time I visit https://open.spotify.com/browse/featured (which I'm logged in to) and try to play some music, I get a dropdown notification saying "The WidevineCdm plugin has crashed", and no music plays.

Here are 3 sample crash  reports:
bp-4f9bdcce-b6f5-4261-98f7-f9ca42170215
bp-9419677f-3b21-4182-bcb0-1e1fa2170215
bp-ebaf4dfc-0d63-4fb2-9411-38a8a2170215

I think this happened to me at some point last week, too. IIRC, a browser restart makes the problem go away. So, we're likely getting ourselves into a broken state that we can't recover from.

Crash backtrace:
 0 	plugin-container 	mozalloc_abort 	memory/mozalloc/mozalloc_abort.cpp:33
1 	libxul.so 	NS_DebugBreak 	xpcom/base/nsDebugImpl.cpp:449
2 	libxul.so 	mozilla::ipc::FatalError 	ipc/glue/ProtocolUtils.cpp:302
3 	libxul.so 	mozilla::gmp::PGMPDecryptorChild::OnMessageReceived 	obj-firefox/ipc/ipdl/PGMPDecryptorChild.cpp:747
4 	libxul.so 	mozilla::gmp::PGMPContentChild::OnMessageReceived 	obj-firefox/ipc/ipdl/PGMPContentChild.cpp:180
5 	libxul.so 	mozilla::ipc::MessageChannel::DispatchAsyncMessage(IPC::Message const&) 	
6 	libxul.so 	libxul.so@0xbfd6d2 	
7 	libxul.so 	mozilla::ipc::MessageChannel::MessageTask::Run() 	
8 	libxul.so 	MessageLoop::DoWork() 	
9 	libxul.so 	base::MessagePumpDefault::Run(base::MessagePump::Delegate*) 	
10 	libxul.so 	MessageLoop::Run()

I'm using Nightly 54.0a1 (2017-02-14) (64-bit) on Ubuntu 16.10
Here's what's in the error console during one of these pageloads:
=========
MediaKeySystemAccess::GetKeySystemStatus(com.widevine.alpha) result=available msg=''
XML Parsing Error: not well-formed
Location: https://spclient.wg.spotify.com/melody/v1/product_state?market=from_token
Line Number 1, Column 1:  product_state:1:1


<unavailable>  web-player.5d824668.js:6
<unavailable>  web-player.5d824668.js:6

MediaKeys.setServerCertificate promise rejected 0x8053000d ''
MediaKeySystemAccess::GetKeySystemStatus(com.widevine.alpha) result=available msg=''
MediaKeys.setServerCertificate promise rejected 0x8053000d ''
Media resource  could not be decoded.  featured

Media resource blob:https://open.spotify.com/06ac3923-5850-49ac-8bde-fc78076e5da7 could not be decoded.  featured

Unix error 2 during operation open on file [path/to/my/firefox/profile]/minidumps/34af7280-9954-e21e-499ec19c-6bea0ff8.extra (No such file or directory)  CrashService.js:39

Media resource blob:https://open.spotify.com/06ac3923-5850-49ac-8bde-fc78076e5da7 could not be decoded.  featured

InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable  web-player.5d824668.js:27

InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable  web-player.5d824668.js:27

Attempt to set a forbidden header was denied: Connection  889283830-lcs_client_bin.js:93:385
Rank: 10
Priority: -- → P1
This is a P1 bug without an assignee. 

P1 are bugs which are being worked on for the current release cycle/iteration/sprint. 

If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.
Keywords: stale-bug
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Is this issue still reproducible?
Flags: needinfo?(dholbert)
I haven't hit it in recent history (and I do visit the Spotify URL from my STR a few times a week).

So, I think it's WFM.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(dholbert)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.