防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

firefox crashes when I go to a page with a video or an animation

  • 6 个回答
  • 1 人有此问题
  • 11 次查看
  • 最后回复者为 philipp

if I go to youtube and select to play it with in a second crashes (and by the way sends you a report) I have done this numerous times. It also happens on websites that automatically start to play something. I have attempted to turn off automatic video add-ons this seems to do nothing, though I'm not sure I am turning off the correct add-on since it still happens. This only started happening in the last 2-3 weeks, before that there was no problem. I run on Windows 10 (ver 16.07).

if I go to youtube and select to play it with in a second crashes (and by the way sends you a report) I have done this numerous times. It also happens on websites that automatically start to play something. I have attempted to turn off automatic video add-ons this seems to do nothing, though I'm not sure I am turning off the correct add-on since it still happens. This only started happening in the last 2-3 weeks, before that there was no problem. I run on Windows 10 (ver 16.07).

被采纳的解决方案

Many thanks philipp and FredMcD. I ran a system file check -- it found no corrupted files, so that at least is good.

I then tried about:config and found media.wmf.enabled and switched it to false. That seemed to work, repeated successful sessions will be the true test. Ever since getting Windows 10 updates (for the last year) it has been one bizarre condition after another.... Do you know why the setting media.wmf.enabled to false fixes the problem?

By the way I don't know what a Windows n-version is. What I have is: Windows 10 Home Version 1607 Os build 14393.447 Ram 8 gb 64-bit operating system x64-based processor

So far so good, Thanks for your help. Bob

定位到答案原位置 👍 0

所有回复 (6)

hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

thanks, is this a windows n version of the operating system by any chance (without including media components by default)?

one thing you could try is to enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named media.wmf.enabled. double-click it and change its value to false.

Most of the flagged programs in the report are Microsoft.

Perform a System File Check to fix corrupted system files Win 7, 8, 10, Vista: https://support.microsoft.com/en-us/kb/929833 Win XP: https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/system_file_checker.mspx?mfr=true

See if there are updates for your graphics drivers https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

选择的解决方案

Many thanks philipp and FredMcD. I ran a system file check -- it found no corrupted files, so that at least is good.

I then tried about:config and found media.wmf.enabled and switched it to false. That seemed to work, repeated successful sessions will be the true test. Ever since getting Windows 10 updates (for the last year) it has been one bizarre condition after another.... Do you know why the setting media.wmf.enabled to false fixes the problem?

By the way I don't know what a Windows n-version is. What I have is: Windows 10 Home Version 1607 Os build 14393.447 Ram 8 gb 64-bit operating system x64-based processor

So far so good, Thanks for your help. Bob

由bobbob3于修改

firefox will depend on your system's codecs to play back non-royalty-free media formats like h.264 or mp3. all your crash reports indicated they were coming from the windows api handling the playback of such unfree formats. (setting media.wmf.enabled to false disabled the support for window's codecs - youtube will recognise that and offer you different file formats like webm that are apparently working without any issue)

other things you could look into for solving this would be an update of your graphics drivers as fred has recommended or uninstalling any third-party codec packs that might interfere here...