media resource could no be decoded




4 years ago
3 years ago


(Reporter: t0mte-bugzilla, Unassigned, Mentored)



37 Branch

Firefox Tracking Flags

(firefox37 affected, firefox38 ?, firefox39 ?, firefox40 ?)




4 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150320202338

Steps to reproduce:

SoundCloud no longer works on Siduction, no problems with FF 36.04. Plugins gstreamer0.10-ffmpeg and gstreamer1.0-libav are installed. For example, try this URL:

Actual results:

In the web console I get this:

Media resource could not be decoded.

Some terminal output:

(process:4326): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

** (firefox:4326): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed

Comment 1

4 years ago
Surely specific to Linux, I cannot reproduce it with FF37 on Win 7.

Could you use the tool mozregression to find a regression range (only the pushlog, no need to bisect), please.
See for details.
Component: Untriaged → Video/Audio
Flags: needinfo?(t0mte-bugzilla)
Product: Firefox → Core

Comment 2

4 years ago
Used mozregression --good-release 36 --bad-release 37
Got pushlog

If you need whole terminal output i could attach a logfile.
Flags: needinfo?(t0mte-bugzilla)

Comment 3

4 years ago
The suspected could be bug 1119302 as this Soundcloud page uses plugins to read MP3.
Component: Video/Audio → Plug-ins
Flags: needinfo?(benjamin)
Keywords: regression

Comment 4

4 years ago
Tomte-bugzilla, do you have any Firefox addons installed? If so, please try disabling them to see if that makes a difference.
Flags: needinfo?(benjamin) → needinfo?(t0mte-bugzilla)

Comment 5

4 years ago
Just tested with a blank && fresh created user-profile without any addons installed: "media resource could no be decoded"
Flags: needinfo?(t0mte-bugzilla)

Comment 6

4 years ago
My team will not be working on this bug because it's not high-enough priority. I will provide some links to help a volunteer diagnose the problem if this is related to bug 1119302. If you have further questions, please feel free to NEEDINFO me.

The new call to check content-policy for plugin loads is at 

If you break at line 509 in a debugger, you can check `rv` and `shouldLoad` to see whether some content policy is rejecting the load. If that's the issue, then you'd have to go back and walk through that method and figure out which content policy is rejecting the load.
Mentor: benjamin


4 years ago

Comment 7

4 years ago
Problem still exists in current beta => FF38.0

Comment 8

4 years ago
Of course because this regression appeared in FF37.

Comment 9

3 years ago
User Agent 	Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID 	20160314030215
OS              Ubuntu 15.04

I tested this on latest Firefox release (v. 45) and latest Nightly (48.0a1) and could not reproduce the problem although I reproduced on Firefox 38. Considering I could reproduce on Firefox 38, but not on current release, I will mark this as Worksforme. If anyone can reproduce the issue on a current build fell free to reopen the bug.
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.