Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Tab always crashes on audio playback

  • 2 replies
  • 0 have this problem
  • 7 views
  • Last reply by fucsi

fucsi
fucsi
more options

I've had this problem for a couple of years already. Not with other browsers and, with the Internet Download Manager extension, I'm usually able to download multimedia content in FF. (That's been my workaround.)

For example, when loading this humble URL ... https://upload.wikimedia.org/wikipedia/commons/transcoded/d/d8/Plattenknistern_record.ogg/Plattenknistern_record.ogg.mp3 ... if I have autoplay enabled, it'll crash right away ("Your tab just crashed"), without autoplay, it'll crash as soon as I hit play. No report gets created under about:crashes.

No difference if I create a new user profile and disable add-ons. Disabling hardware acceleration doesn't help either. I can't do without most of my settings and add-ons, so refreshing FF is not an option. I'd sooner try a new install (and then import my profile and reinstall add-ons), but that's laborious, not guaranteed to solve the problem, and I figure that there ought to be some way to diagnose a crash in such straightforward circumstances? Telling the JS debugger to pause on exceptions seems to be no help.

Twitter videos used to work, albeit without audio, so long as I didn't pause and then resume playback. Lately, after upgrading from FF 104 to 105 (or possibly through a change on Twitter's end), I get "the media could not be played."

I've had this problem for a couple of years already. Not with other browsers and, with the Internet Download Manager extension, I'm usually able to download multimedia content in FF. (That's been my workaround.) For example, when loading this humble URL ... https://upload.wikimedia.org/wikipedia/commons/transcoded/d/d8/Plattenknistern_record.ogg/Plattenknistern_record.ogg.mp3 ... if I have autoplay enabled, it'll crash right away ("Your tab just crashed"), without autoplay, it'll crash as soon as I hit play. No report gets created under about:crashes. No difference if I create a new user profile and disable add-ons. Disabling hardware acceleration doesn't help either. I can't do without most of my settings and add-ons, so refreshing FF is not an option. I'd sooner try a new install (and then import my profile and reinstall add-ons), but that's laborious, not guaranteed to solve the problem, and I figure that there ought to be some way to diagnose a crash in such straightforward circumstances? Telling the JS debugger to pause on exceptions seems to be no help. Twitter videos used to work, albeit without audio, so long as I didn't pause and then resume playback. Lately, after upgrading from FF 104 to 105 (or possibly through a change on Twitter's end), I get "the media could not be played."

All Replies (2)

Paul
Paul
  • Moderator
  • Top 10 Contributor
more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

  1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
  2. Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Fx64Beta-aboutcrashes-unsubmitted

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

fucsi
fucsi Question owner
more options

Thanks, Paul. These crashes don't seem to result in a report; my about:crashes page only says that "No crash reports have been submitted" and shows no unsubmitted reports either. I've now noticed that an application error gets listed in Windows Event Viewer; says that the "faulting module" is kernelbase.dll. Perhaps this explains why Firefox doesn't generate a crash report.

Faulting application name: firefox.exe, version: 105.0.0.8293, time stamp: 0x63235163 Faulting module name: KERNELBASE.dll, version: 6.3.9600.20369, time stamp: 0x626a18c2 Exception code: 0xc06d007e Fault offset: 0x0000000000008d5c Faulting process id: 0x1c68 Faulting application start time: 0x01d8d0ebcaa017c1 Faulting application path: C:\Program Files\Mozilla Firefox Quantum\firefox.exe Faulting module path: C:\Windows\system32\KERNELBASE.dll