1309012 - Firefox doesn't play mp3 files when first started (but will on restart)

Status: RESOLVED DUPLICATE of bug 1317234

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

Description

[Steve Chessin]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:49.0) Gecko/20100101 Firefox/49.0
Build ID: 20160922113459

Steps to reproduce:

Rebooted my system, started Firefox, opened an MP3 file.


Actual results:

Got a reverse spinner and no sound. I then quit Firefox (which caused it to go Not Responding and then crash; see bug 1308629) and restarted it, and this time the MP3 file played. (I have Firefox set to "Show my windows and tabs from last time" when it starts, so it automatically reloaded the MP3 file.)


Expected results:

It should have loaded the file and played it the first time.

Comment 1

[Steve Chessin]

I first noticed this on FF 49.0. (I'm now on FF 49.0.1.) It didn't happen with FF 48.0.1.

Note that the MP3 file is on my hard drive (that is, a URL beginning file:///Users/steve/....), so networking is not an issue.

Comment 3

[Jean-Yves Avenard [:jya]]

Why would you mark this bug as a duplicate? it doesn't look anywhere close to it...

Comment 4

[Emil Pasca [:emilpasca]]

I have tested this issue on Mac OS X 10.9 and Mac OS X 10.10 with Firefox(49.0), the latest Firefox release (49.0.1) and the latest Nightly (52.0a1-20161012143919) and could not to reproduce it.
When loading a MP3 media file in the browser, the file is loaded properly and when pressing the "play" button, the sound is also played.

As mentioned in the description from this bug report, the browser stopped responding when the reporter tried to open a media file, than as the user described in (bug 1308629), he tried closing the browser by pressing Ctrl + Q, which eventually had to be force quit, causing the crashes which have been added to that bug report.

Because of this, I'm assuming that this bug report is describing the steps done by the reporter before submitting the aforementioned bug  and should be marked as a duplicate of that one.

Comment 5

[Steve Chessin]

I have no evidence that they are related. In fact, I recently quit FF (because it was consuming over 3GB of memory), I think it crashed (I've stopped keeping track), I restarted it, the MP3 didn't play, so I quit it again, it did NOT crash, I restarted it, and the MP3 did play.

Comment 6

[Emil Pasca [:emilpasca]]

Since this issue is not related to the other one, we should go to the usual steps in order to identify the cause of this.
1) First of all please retest this using a new clean Firefox profile, in order to check if this was not caused by any customization settings or addons.
2) You could also try this in safe mode https://goo.gl/PNe90E, in order to eliminate any other custom settings as a possible cause.
3) Finally could you also check if the issue is reproducible on latest Nightly build (https://nightly.mozilla.org/)?

Comment 7

[Steve Chessin]

(In reply to Emil Pasca [:emilpasca] from comment #6)
> Since this issue is not related to the other one, we should go to the usual
> steps in order to identify the cause of this.
> 1) First of all please retest this using a new clean Firefox profile, in
> order to check if this was not caused by any customization settings or
> addons.

How do I do that destroying my current profile?

> 2) You could also try this in safe mode https://goo.gl/PNe90E, in order to
> eliminate any other custom settings as a possible cause.

I tried that, but I guess I didn't hold down the option key long enough. It came up normally and didn't play the mp3. So I went to restart in safe mode but in the menu clicked the quit button instead of the help button by mistake. Firefox crashed (see https://crash-stats.mozilla.com/report/index/bp-f9d8e377-4809-4c75-a7bb-39e292161017) and I told Crash Reporter to restart Firefox and this time the mp3 played.

> 3) Finally could you also check if the issue is reproducible on latest
> Nightly build (https://nightly.mozilla.org/)?

I have a day job. Since I appear to have a workaround (quit Firefox and restart it), trouble-shooting is going to be a low priority for me until the workaround no longer works.

Comment 8

[Steve Chessin]

(In reply to Steve Chessin from comment #7)
> (In reply to Emil Pasca [:emilpasca] from comment #6)
> > Since this issue is not related to the other one, we should go to the usual
> > steps in order to identify the cause of this.
> > 1) First of all please retest this using a new clean Firefox profile, in
> > order to check if this was not caused by any customization settings or
> > addons.
> 
> How do I do that destroying my current profile?

I mean without destroying my current profile?

Comment 9

[Emil Pasca [:emilpasca]]

(In reply to Steve Chessin from comment #8)
> 
> > How do I do that destroying my current profile?
> 
> I mean without destroying my current profile?

Probably the most easy and fastest way to do this on Mac OS X, is by following the next steps:
1) Open a new terminal.
2) Open the application folder and drag "Firefox" app into the terminal.
3) Add the following text in the terminal "/Contents/MacOS/firefox -p -no-remote".
By now, you should have something like this: "Applications/Firefox.app/Contents/MacOS/firefox -p -no-remote"
4) Press the "Enter" key and the profile manager should pop-up, displaying the "default" option which is your main profile and also some other options like "Create Profile" and so on...
5) Press the "Create Profile" button and after creating your profile and selecting it, you can press the "Start Firefox" button.


Also:
> I tried that, but I guess I didn't hold down the option key long enough. It came up
> normally and didn't play the mp3. So I went to restart in safe mode but in the menu
> clicked the quit button instead of the help button by mistake. Firefox crashed (see 
> https://crash-stats.mozilla.com/report/index/bp-f9d8e377-4809-4c75-a7bb-39e292161017)
> and I told Crash Reporter to restart Firefox and this time the mp3 played.

After the browser crashed, it probably didn't start in safe mode, could you please try to retest this by restarting Firefox in safe mode.

The Nightly channel, has the latest changes and features included and the issue might be fixed there, due to the fact that I cannot reproduce this on my system, I would kindly ask you, that whenever you might have time to also test this for us. Knowing if the issue is still reproducible on the Nightly channel can help us in solving this.

Comment 10

[Steve Chessin]

(In reply to Emil Pasca [:emilpasca] from comment #9)
> (In reply to Steve Chessin from comment #8)
> > 
> > > How do I do that destroying my current profile?
> > 
> > I mean without destroying my current profile?
> 
> Probably the most easy and fastest way to do this on Mac OS X, is by
> following the next steps:
> 1) Open a new terminal.
> 2) Open the application folder and drag "Firefox" app into the terminal.
> 3) Add the following text in the terminal "/Contents/MacOS/firefox -p
> -no-remote".
> By now, you should have something like this:
> "Applications/Firefox.app/Contents/MacOS/firefox -p -no-remote"
> 4) Press the "Enter" key and the profile manager should pop-up, displaying
> the "default" option which is your main profile and also some other options
> like "Create Profile" and so on...
> 5) Press the "Create Profile" button and after creating your profile and
> selecting it, you can press the "Start Firefox" button.
> 
> 
> Also:
> > I tried that, but I guess I didn't hold down the option key long enough. It came up
> > normally and didn't play the mp3. So I went to restart in safe mode but in the menu
> > clicked the quit button instead of the help button by mistake. Firefox crashed (see 
> > https://crash-stats.mozilla.com/report/index/bp-f9d8e377-4809-4c75-a7bb-39e292161017)
> > and I told Crash Reporter to restart Firefox and this time the mp3 played.
> 
> After the browser crashed, it probably didn't start in safe mode, could you
> please try to retest this by restarting Firefox in safe mode.
> 
> The Nightly channel, has the latest changes and features included and the
> issue might be fixed there, due to the fact that I cannot reproduce this on
> my system, I would kindly ask you, that whenever you might have time to also
> test this for us. Knowing if the issue is still reproducible on the Nightly
> channel can help us in solving this.

I will try these the next time I need to restart Firefox (which I do at least once a week since over time it increases both its own and the kernel's use of memory).

Comment 11

[Jean-Yves Avenard [:jya]]

Are you starting firefox in 32 bits mode by any chance?
could you copy the output of about:support ? thank you

Comment 12

[Steve Chessin]

(In reply to Jean-Yves Avenard [:jya] from comment #11)
> Are you starting firefox in 32 bits mode by any chance?

I didn't think that option was available on MacOS. In any event, I don't know how to do that so I assume it isn't happening.

> could you copy the output of about:support ? thank you

Here it is as text. Let me know if you would prefer raw data. (I don't see anything that says whether it's running the x86_64 or i386 binary.)

Application Basics
------------------

Name: Firefox
Version: 49.0.1
Build ID: 20160922113459
Update Channel: release
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:49.0) Gecko/20100101 Firefox/49.0
OS: Darwin 13.4.0
Multiprocess Windows: 0/7 (Disabled by add-ons)
Safe Mode: false

Crash Reports for the Last 3 Days
---------------------------------

Report ID: bp-f9d8e377-4809-4c75-a7bb-39e292161017
Submitted: 2 days ago

All Crash Reports

Extensions
----------

Name: Add to Search Bar
Version: 2.9
Enabled: true
ID: [e-mail]

Name: Better Bug
Version: 8.7.1
Enabled: true
ID: {7cad0727-da80-44e6-ab41-2fe3875883fe}

Name: Flashblock
Version: 1.5.20
Enabled: true
ID: {3d7eb24f-2740-49df-8937-200b1cc08f8a}

Name: Multi-process staged rollout
Version: 1.2
Enabled: true
ID: [e-mail]

Name: NoScript
Version: 2.9.0.14
Enabled: true
ID: {73a6fe31-595d-460b-a920-fcc0f8843232}

Name: Pocket
Version: 1.0.4
Enabled: true
ID: [e-mail]

Name: Tab Groups
Version: 2.0.1
Enabled: true
ID: tabgroups@quicksaver

Name: Troubleshooter
Version: 1.1a.1-signed.1-signed
Enabled: true
ID: [e-mail]

Name: Web Compat
Version: 1.0
Enabled: true
ID: [e-mail]

Name: WOT
Version: 20151208
Enabled: true
ID: {a0d7ccb3-214d-498b-b4aa-0e8fda9a7bf7}

Name: Bobsled by T-Mobile
Version: 1.20.3.16608
Enabled: false
ID: {E95CD7A3-A1D1-42b3-8CD5-CD483F11C7FE}

Graphics
--------

Features
Compositing: OpenGL
Asynchronous Pan/Zoom: none
WebGL Renderer: NVIDIA Corporation -- NVIDIA GeForce 9400M OpenGL Engine
Hardware H264 Decoding: Yes
GPU #1
Active: Yes
Vendor ID: 0x10de
Device ID: 0x0863

Diagnostics
AzureCanvasAccelerated: 1
AzureCanvasBackend: skia
AzureContentBackend: skia
AzureFallbackCanvasBackend: none





Important Modified Preferences
------------------------------

accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 358400
browser.cache.disk.filesystem_reported: 1
browser.cache.disk.hashstats_reported: 1
browser.cache.disk.smart_size_cached_value: 358400
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.frecency_experiment: 1
browser.download.folderList: 2
browser.download.importedFromSqlite: true
browser.download.manager.closeWhenDone: true
browser.fixup.domainwhitelist.homeportal: true
browser.places.importBookmarksHTML: false
browser.places.smartBookmarksVersion: 8
browser.search.useDBForOrder: true
browser.sessionstore.upgradeBackup.latestBuildID: 20160922113459
browser.startup.homepage: http://my.oracle.com/
browser.startup.homepage_override.buildID: 20160922113459
browser.startup.homepage_override.mstone: 49.0.1
browser.tabs.onTop: false
browser.tabs.remote.autostart.2: true
browser.urlbar.userMadeSearchSuggestionsChoice: true
browser.zoom.siteSpecific: false
dom.apps.lastUpdate.buildID: 20160922113459
dom.apps.lastUpdate.mstone: 49.0.1
dom.apps.reset-permissions: true
dom.max_chrome_script_run_time: 40
dom.max_script_run_time: 0
dom.mozApps.used: true
extensions.lastAppVersion: 49.0.1
font.internaluseonly.changed: true
gfx.crash-guard.glcontext.appVersion: 45.0.2
gfx.crash-guard.glcontext.deviceID: 0x0863
gfx.crash-guard.status.glcontext: 2
media.benchmark.vp9.fps: 81
media.benchmark.vp9.versioncheck: 1
media.gmp-gmpopenh264.abi: x86_64-gcc3-u-i386-x86_64
media.gmp-gmpopenh264.lastUpdate: 1471549961
media.gmp-gmpopenh264.version: 1.6
media.gmp-manager.buildID: 20160922113459
media.gmp-manager.lastCheck: 1476914686
media.gmp-widevinecdm.abi: x86_64-gcc3-u-i386-x86_64
media.gmp-widevinecdm.lastUpdate: 1474685352
media.gmp-widevinecdm.version: 1.4.8.903
media.gmp.storage.version.observed: 1
media.webrtc.debug.aec_log_dir: /Users/steve/Library/Caches/TemporaryItems
media.webrtc.debug.log_file: /Users/steve/Library/Caches/TemporaryItems/WebRTC.log
network.cookie.prefsMigrated: true
network.predictor.cleaned-up: true
places.database.lastMaintenance: 1476738772
places.history.expiration.transient_current_max_pages: 104858
plugin.disable_full_page_plugin_for_types: audio/ac3,application/pdf
plugin.importedState: true
plugin.state.adobepdfviewernpapi: 2
plugin.state.java: 2
print.print_bgcolor: false
print.print_bgimages: true
print.print_colorspace:
print.print_command:
print.print_downloadfonts: true
print.print_duplex: 0
print.print_evenpages: true
print.print_in_color: true
print.print_margin_bottom: 0.5
print.print_margin_left: 0.5
print.print_margin_right: 0.5
print.print_margin_top: 0.5
print.print_oddpages: true
print.print_orientation: 0
print.print_page_delay: 50
print.print_pagedelay: 500
print.print_paper_data: 0
print.print_paper_height: 11.00
print.print_paper_name:
print.print_paper_size: 666
print.print_paper_size_type: 1
print.print_paper_size_unit: 0
print.print_paper_width: 8.50
print.print_plex_name:
print.print_printer:
print.print_resolution: 0
print.print_resolution_name:
print.print_reversed: false
print.print_scaling: 1.00
print.print_shrink_to_fit: true
print.print_to_file: false
print.print_unwriteable_margin_bottom: 17
print.print_unwriteable_margin_left: 17
print.print_unwriteable_margin_right: 17
print.print_unwriteable_margin_top: 17
print.printer_ussca17-2-b501.print_bgcolor: false
print.printer_ussca17-2-b501.print_bgimages: true
print.printer_ussca17-2-b501.print_duplex: 0
print.printer_ussca17-2-b501.print_edge_bottom: 0
print.printer_ussca17-2-b501.print_edge_left: 0
print.printer_ussca17-2-b501.print_edge_right: 0
print.printer_ussca17-2-b501.print_edge_top: 0
print.printer_ussca17-2-b501.print_evenpages: true
print.printer_ussca17-2-b501.print_footercenter:
print.printer_ussca17-2-b501.print_footerleft: &PT
print.printer_ussca17-2-b501.print_footerright: &D
print.printer_ussca17-2-b501.print_headercenter:
print.printer_ussca17-2-b501.print_headerleft: &T
print.printer_ussca17-2-b501.print_headerright: &U
print.printer_ussca17-2-b501.print_in_color: true
print.printer_ussca17-2-b501.print_margin_bottom: 0.5
print.printer_ussca17-2-b501.print_margin_left: 0.5
print.printer_ussca17-2-b501.print_margin_right: 0.5
print.printer_ussca17-2-b501.print_margin_top: 0.5
print.printer_ussca17-2-b501.print_oddpages: true
print.printer_ussca17-2-b501.print_orientation: 0
print.printer_ussca17-2-b501.print_page_delay: 50
print.printer_ussca17-2-b501.print_paper_data: 0
print.printer_ussca17-2-b501.print_paper_height: 11.00
print.printer_ussca17-2-b501.print_paper_name:
print.printer_ussca17-2-b501.print_paper_size_type: 1
print.printer_ussca17-2-b501.print_paper_size_unit: 0
print.printer_ussca17-2-b501.print_paper_width: 8.50
print.printer_ussca17-2-b501.print_resolution: 0
print.printer_ussca17-2-b501.print_reversed: false
print.printer_ussca17-2-b501.print_scaling: 1.00
print.printer_ussca17-2-b501.print_shrink_to_fit: true
print.printer_ussca17-2-b501.print_to_file: false
print.printer_ussca17-2-b501.print_unwriteable_margin_bottom: 17
print.printer_ussca17-2-b501.print_unwriteable_margin_left: 17
print.printer_ussca17-2-b501.print_unwriteable_margin_right: 17
print.printer_ussca17-2-b501.print_unwriteable_margin_top: 17
privacy.clearOnShutdown.cookies: false
privacy.clearOnShutdown.downloads: false
privacy.clearOnShutdown.history: false
privacy.cpd.downloads: false
privacy.cpd.formdata: false
privacy.cpd.history: false
privacy.item.downloads: false
privacy.item.history: false
privacy.sanitize.migrateClearSavedPwdsOnExit: true
privacy.sanitize.migrateFx3Prefs: true
privacy.sanitize.timeSpan: 0
security.disable_button.openCertManager: false
security.disable_button.openDeviceManager: false
security.OCSP.disable_button.managecrl: false
security.sandbox.content.tempDirSuffix: {efe05783-4849-4c4f-85be-bf0afc3b8f19}
security.ssl.errorReporting.automatic: true
security.tls.insecure_fallback_hosts: fruid-tools.us.oracle.com,ilomsvn.us.oracle.com,ilomsvn-viewvc.us.oracle.com,ilomsvn-prefs.us.oracle.com
security.warn_viewing_mixed: false
services.sync.declinedEngines:
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1474502946

Important Locked Preferences
----------------------------

Places Database
---------------

JavaScript
----------

Incremental GC: true

Accessibility
-------------

Activated: false
Prevent Accessibility: 0

Library Versions
----------------

NSPR
Expected minimum version: 4.12
Version in use: 4.12

NSS
Expected minimum version: 3.25
Version in use: 3.25

NSSSMIME
Expected minimum version: 3.25
Version in use: 3.25

NSSSSL
Expected minimum version: 3.25
Version in use: 3.25

NSSUTIL
Expected minimum version: 3.25
Version in use: 3.25

Experimental Features
---------------------

Comment 13

[Jean-Yves Avenard [:jya]]

(In reply to Steve Chessin from comment #12)
> (In reply to Jean-Yves Avenard [:jya] from comment #11)
> > Are you starting firefox in 32 bits mode by any chance?
> 
> I didn't think that option was available on MacOS. In any event, I don't
> know how to do that so I assume it isn't happening.

If you right click on the Firefox.app package (easiest way to show the Firefox bundle in the Finder, is to command-click on the Firefox icon in the Dock), click on Get Info, do you have "open in 32-bit mode" checked?
You can also start the "Activity Monitor" and select the "CPU" tab; look for the line with Firefox in it, there's a "Kind" column, it will show 32 bit or 64 bit...

Comment 14

[Jean-Yves Avenard [:jya]]

You could also start firefox in Safe Mode, and see if it still occurs, that will indicate that the issue is with one of the extension you installed.

Comment 15

[Steve Chessin]

(In reply to Jean-Yves Avenard [:jya] from comment #13)
> (In reply to Steve Chessin from comment #12)
> > (In reply to Jean-Yves Avenard [:jya] from comment #11)
> > > Are you starting firefox in 32 bits mode by any chance?
> > 
> > I didn't think that option was available on MacOS. In any event, I don't
> > know how to do that so I assume it isn't happening.
> 
> If you right click on the Firefox.app package (easiest way to show the
> Firefox bundle in the Finder, is to command-click on the Firefox icon in the
> Dock), click on Get Info, do you have "open in 32-bit mode" checked?

It is not checked.

> You can also start the "Activity Monitor" and select the "CPU" tab; look for
> the line with Firefox in it, there's a "Kind" column, it will show 32 bit or
> 64 bit...

Activity Monitor (which I keep open all the time) says 64 bit.

Comment 16

[Steve Chessin]

(In reply to Emil Pasca [:emilpasca] from comment #6)
> Since this issue is not related to the other one, we should go to the usual
> steps in order to identify the cause of this.
> 1) First of all please retest this using a new clean Firefox profile, in
> order to check if this was not caused by any customization settings or
> addons.
> 2) You could also try this in safe mode https://goo.gl/PNe90E, in order to
> eliminate any other custom settings as a possible cause.
> 3) Finally could you also check if the issue is reproducible on latest
> Nightly build (https://nightly.mozilla.org/)?

I tried Nightly 52.0a1 (2016-10-18) (64-bit) (NOT in safe mode and NOT with a new clean profile) and it didn't happen (the mp3 played). OTOH, it doesn't always happen when I launch FF49.0.1. I also didn't launch Nightly immediately after a reboot, so I'll need to try that test next time I reboot.

BTW, Nightly is complaining that "WOT might be making Nightly run slowly". I like WOT as it warns me about suspect web sites.

Comment 17

[Steve Chessin]

Nightly isn't working with Webex so I'm going back to the FF49.0.2

Comment 18

[Steve Chessin]

I rebooted my MacBookPro and restarted Nightly 52.0a1 and the mp3 did NOT play. I will now quit and restart Nightly and see what happens.

Comment 19

[Steve Chessin]

I Quit and restarted Nightly and this time the mp3 played. I will now Quit Nightly and start FF49.0.2 in Safe Mode (but since that won't be right after a reboot, that might not be a valid test).

Comment 20

[Steve Chessin]

I started FF49.0.2 in Safe Mode and it did NOT play the MP3. I'll now quit it and restart it in Safe Mode again and see what happens.

BTW, normally I have 14 plugins but when I start Nightly it only shows 4 of them. Why is that?

Comment 21

[Steve Chessin]

The Quit from Safe Mode crashed (of course); see https://crash-stats.mozilla.com/report/index/bp-19904271-b812-453b-bd9f-1b43e2161024

I restarted FF49.0.2 in Safe Mode after the Quit that crashed and the MP3 did play. I will try the clean profile the next time I have to restart FF as I have to go back to my day job now.

Is this (Comments 18-21) enough information or do you still need the clean profile test?

BTW, nightly also crashed on Quit; see https://crash-stats.mozilla.com/report/index/33e7bb59-3a22-40f6-add9-c1d902161024

Comment 22

[Jean-Yves Avenard [:jya]]

What MP3 are you actually playing?

The crash report shows that 4 threads are blocked on
https://hg.mozilla.org/releases/mozilla-release/annotate/7356baae8e73/dom/media/platforms/apple/AppleVTDecoder.cpp#l245

Which is the H264 decoder.. 
appears that the VideoToolbox is stuck on waiting for something, 
There are two blocked AppleGVA too, which searching indicates are hardware accelerator.

What mac do you have??
I see a nvidia 9400M in the graphic report. That the code is stuck on two AppleGVA while 4 H264 decoders are stuck is highly suspicious. The 9400M is an ancient GPU (2008ish) and you couldn't create more than 2 hardware decoders with it.

Maybe we should blacklist hardware decoding on those machines...

Comment 23

[Steve Chessin]

(In reply to Jean-Yves Avenard [:jya] from comment #22)
> What MP3 are you actually playing?

A local file that I downloaded from an company internal website.

> The crash report shows that 4 threads are blocked on
> https://hg.mozilla.org/releases/mozilla-release/annotate/7356baae8e73/dom/
> media/platforms/apple/AppleVTDecoder.cpp#l245
> 
> Which is the H264 decoder.. 
> appears that the VideoToolbox is stuck on waiting for something, 
> There are two blocked AppleGVA too, which searching indicates are hardware
> accelerator.
> 
> What mac do you have??

I have a MacBookPro5,3 (MacBookPro(15-inch,Mid2009,2.8GHz))

It has two internal graphics "cards": a NVIDIA GeForce 9400M, and a NVIDIA GeForce 9600M GT. I almost always run it with the 9400M for "Better battery life" but perhaps I should change the setting to "Higher performance" to use the 9600M?

> I see a nvidia 9400M in the graphic report. That the code is stuck on two
> AppleGVA while 4 H264 decoders are stuck is highly suspicious. The 9400M is
> an ancient GPU (2008ish) and you couldn't create more than 2 hardware
> decoders with it.

How would that explain that FF won't play an MP3 on the first FF start after a reboot, but will on a restart of FF?

> Maybe we should blacklist hardware decoding on those machines...

Or maybe you should just fix the bugs... :-)

Comment 24

[Jean-Yves Avenard [:jya]]

(In reply to Steve Chessin from comment #23)
> (In reply to Jean-Yves Avenard [:jya] from comment #22)
> > What MP3 are you actually playing?
> 
> A local file that I downloaded from an company internal website.

Any chance you could attach it here?

> 
> > The crash report shows that 4 threads are blocked on
> > https://hg.mozilla.org/releases/mozilla-release/annotate/7356baae8e73/dom/
> > media/platforms/apple/AppleVTDecoder.cpp#l245
> > 
> > Which is the H264 decoder.. 
> > appears that the VideoToolbox is stuck on waiting for something, 
> > There are two blocked AppleGVA too, which searching indicates are hardware
> > accelerator.
> > 
> > What mac do you have??
> 
> I have a MacBookPro5,3 (MacBookPro(15-inch,Mid2009,2.8GHz))
> 
> It has two internal graphics "cards": a NVIDIA GeForce 9400M, and a NVIDIA
> GeForce 9600M GT. I almost always run it with the 9400M for "Better battery
> life" but perhaps I should change the setting to "Higher performance" to use
> the 9600M?

It would be interesting to see if forcing the 9600M help alleviate the problem.


> 
> > I see a nvidia 9400M in the graphic report. That the code is stuck on two
> > AppleGVA while 4 H264 decoders are stuck is highly suspicious. The 9400M is
> > an ancient GPU (2008ish) and you couldn't create more than 2 hardware
> > decoders with it.
> 
> How would that explain that FF won't play an MP3 on the first FF start after
> a reboot, but will on a restart of FF?
I don't know why playing a MP3 would cause the issue to occur, the code where it's sucked is only ever reached if you're playing a MP4 with a h264 video track.
So you may have restored a Firefox session which had several videos playing and it's attempting to play them all at once. 

My guess is that upon restart, not all drivers have finished loading, timing of events etc...

We could maybe serialise how h264 decoders are created so you can never create a decoder before a previous one has finished initialising.
Seems to be a deadlock in 10.9 kernel..

> 
> > Maybe we should blacklist hardware decoding on those machines...
> 
> Or maybe you should just fix the bugs... :-)

There's nothing we can fix here... it's all happening on Apple's internal video framework, which we must rely on.
So at best we can work around the issue. At least you're not getting kernel panic, which is typically how Apple's bug manifest themselves. 
You could always update from 10.9 it's fairly old and receive almost no security updates anymore. 

In the line of constructive comments, I could also add that maybe your employer could update your machines, 7 years is kind of pushing past the lifecycle of a laptop :)

Comment 25

[Steve Chessin]

(In reply to Jean-Yves Avenard [:jya] from comment #24)
> (In reply to Steve Chessin from comment #23)
> > (In reply to Jean-Yves Avenard [:jya] from comment #22)
> > > What MP3 are you actually playing?
> > 
> > A local file that I downloaded from an company internal website.
> 
> Any chance you could attach it here?

The file is company confidential, but I'll see if I can recreate it with one of the public mp3's I have on my machine and attach that.

> In the line of constructive comments, I could also add that maybe your
> employer could update your machines, 7 years is kind of pushing past the
> lifecycle of a laptop :)

It gets complicated. My former employer would provide either Wintel or Apple (employee choice), but we were acquired by my current employer who will only update to Wintel.

Comment 26

[Emil Pasca [:emilpasca]]

If for privacy reasons, you can't provide us with the mp3 you're using when reproducing the issue, can you please try to reproduce this with a public mp3 and attached that one to this bug report so we can also re-test this?

Thank you.

Comment 27

[Emil Pasca [:emilpasca]]

Marking this as Resolved - Incomplete due to the lack of response from the reporter.

If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.

Comment 28

[Steve Chessin]

(In reply to Emil Pasca [:emilpasca] from comment #27)
> Marking this as Resolved - Incomplete due to the lack of response from the
> reporter.
> 
> If anyone can still reproduce it on latest versions, feel free to reopen the
> issue and provide more information.

I'm sorry to take so long to get back to you. Between my day job, the Thanksgiving holiday, and a death in the family, I've had other things on my mind. (Besides, I do have a workaround: reboot, relaunch, quit, relaunch.)

But I have done a lot of experiments in the meantime. Here's a summary:

Launched FF49.0.2 with clean profile after a reboot. MP3 did not play.
Quit FF, restarted it, and it did play. Quit FF.

Launched FF49.0.2 with default profile, did not play. Quit, launched again, did play.

Accidentally quit FF49.0.2, so relaunched it; did not play. So Quit it (it crashed), relaunched it, and still did not play.

Rebooted system. Launched FF49.0.2, did not play. Quit FF, it crashed, relaunched, it played.

Swithced to NVIDIA GeForce 9600M GT graphic device, rebooted, started FF50.0.0, just kept spinning. 
Quit FF, it crashed, relaunched, didn't play.

Rebooted, started FF50.0.0, didn't play. Quit FF, it crashed, relaunched, played.

Now the MP3 I've been using is invoked by (embedded in?) an HTML5 file. I haven't tried a naked MP3 file yet, but now that I've finished viewing and listening to the hour-and-a-half presentation, I'll do the experiments (as I find time) with a naked public MP3 file. I do note that when the MP3 invoked by the HTML5 file doesn't play, neither do the naked MP3 files. But I'll close the HTML5 tab now so that on launch it tries the naked MP3 files first.

Comment 29

[Emil Pasca [:emilpasca]]

Due to the fact that the issue is reproducible for the reporter I will assign a component and perhaps there's someone with extensive knowledge on this area that might be able to help here.

Comment 30

[Steve Chessin]

(In reply to Steve Chessin from comment #28)
> (In reply to Emil Pasca [:emilpasca] from comment #27)
> > Marking this as Resolved - Incomplete due to the lack of response from the
> > reporter.
> > 
> > If anyone can still reproduce it on latest versions, feel free to reopen the
> > issue and provide more information.
> 
> I'm sorry to take so long to get back to you. Between my day job, the
> Thanksgiving holiday, and a death in the family, I've had other things on my
> mind. (Besides, I do have a workaround: reboot, relaunch, quit, relaunch.)
> 
> But I have done a lot of experiments in the meantime. Here's a summary:
> 
> Launched FF49.0.2 with clean profile after a reboot. MP3 did not play.
> Quit FF, restarted it, and it did play. Quit FF.
> 
> Launched FF49.0.2 with default profile, did not play. Quit, launched again,
> did play.
> 
> Accidentally quit FF49.0.2, so relaunched it; did not play. So Quit it (it
> crashed), relaunched it, and still did not play.
> 
> Rebooted system. Launched FF49.0.2, did not play. Quit FF, it crashed,
> relaunched, it played.
> 
> Swithced to NVIDIA GeForce 9600M GT graphic device, rebooted, started
> FF50.0.0, just kept spinning. 
> Quit FF, it crashed, relaunched, didn't play.
> 
> Rebooted, started FF50.0.0, didn't play. Quit FF, it crashed, relaunched,
> played.
> 
> Now the MP3 I've been using is invoked by (embedded in?) an HTML5 file. I
> haven't tried a naked MP3 file yet, but now that I've finished viewing and
> listening to the hour-and-a-half presentation, I'll do the experiments (as I
> find time) with a naked public MP3 file. I do note that when the MP3 invoked
> by the HTML5 file doesn't play, neither do the naked MP3 files. But I'll
> close the HTML5 tab now so that on launch it tries the naked MP3 files first.

I haven't been able to reproduce the problem with a "naked" MP3 file. I rebooted, started FF50.0.2, it played the naked MP3 file, but as it wasn't the first tab (so not auto-loaded on startup) I'm not sure it was a valid test.

So I set it up so the MP3 file was the first tab of that window. I rebooted, started FF50.0.2, and it played the MP3 file.

Comment 31

[JW Wang [:jwwang] [:jw_wang]]

Sounds like bug 1317234. Let's see if bug 1317234 fixes the issue here.

Comment 32

[Alex Chronopoulos [:achronop]]

(In reply to Steve Chessin from comment #28)
 
> Accidentally quit FF49.0.2, so relaunched it; did not play. So Quit it (it
> crashed), relaunched it, and still did not play.
> 
> Rebooted system. Launched FF49.0.2, did not play. Quit FF, it crashed,
> relaunched, it played.
> 
> Swithced to NVIDIA GeForce 9600M GT graphic device, rebooted, started
> FF50.0.0, just kept spinning. 
> Quit FF, it crashed, relaunched, didn't play.
> 
> Rebooted, started FF50.0.0, didn't play. Quit FF, it crashed, relaunched,
> played.

If you have the crash reports from the crashes above we can tell if it is a duplicate of bug 1317234.

Comment 33

[Steve Chessin]

(In reply to Alex Chronopoulos [:achronop] from comment #32)
> (In reply to Steve Chessin from comment #28)
>  
> > Accidentally quit FF49.0.2, so relaunched it; did not play. So Quit it (it
> > crashed), relaunched it, and still did not play.
> > 
> > Rebooted system. Launched FF49.0.2, did not play. Quit FF, it crashed,
> > relaunched, it played.
> > 
> > Swithced to NVIDIA GeForce 9600M GT graphic device, rebooted, started
> > FF50.0.0, just kept spinning. 
> > Quit FF, it crashed, relaunched, didn't play.
> > 
> > Rebooted, started FF50.0.0, didn't play. Quit FF, it crashed, relaunched,
> > played.
> 
> If you have the crash reports from the crashes above we can tell if it is a
> duplicate of bug 1317234.

I don't remember which was which, but here are the crash reports from that period:
https://crash-stats.mozilla.com/report/index/3b003e51-fb0a-4716-a238-afd512161103
https://crash-stats.mozilla.com/report/index/f9242262-385b-4d6d-9cd1-b3e1d2161109
https://crash-stats.mozilla.com/report/index/2cf334b1-d641-49e4-b489-627832161114
https://crash-stats.mozilla.com/report/index/9ff52ce4-fe8a-497c-bd8e-85e4c2161118
https://crash-stats.mozilla.com/report/index/bf733647-72f5-44b7-9e4c-8bcb02161119
https://crash-stats.mozilla.com/report/index/b3c82462-4c92-4bd7-adb1-081a62161123
https://crash-stats.mozilla.com/report/index/577a4ae6-a18b-46da-8595-dafda2161126
https://crash-stats.mozilla.com/report/index/ad315f27-59b6-4023-9015-cb27f2161127
https://crash-stats.mozilla.com/report/index/ec6878c7-2ba8-4412-bcfb-75fb32161128

Comment 34

[Jean-Yves Avenard [:jya]]

This first crash is in graphics.

The following 5 looks like bug 1354294.

Are you using LastPass addon by any chance?

Comment 35

[Steve Chessin]

(In reply to Jean-Yves Avenard [:jya] from comment #34)
> This first crash is in graphics.
> 
> The following 5 looks like bug 1354294.
> 
> Are you using LastPass addon by any chance?

No. The addons (extensions) I have enabled are:
Add to Search Bar
Better Bug
Cisco WebEx Extension
Flashblock
NoScript
Tab Groups
Troubleshooter

I also have these plug-ins:
OpenH264 Video Codec provided by Cisco Systems, Inc.
Shockwave Flash
Widevine Content Decryption Module provided by Google Inc. (Hmmm. I don't recall installing that plug-in.)