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

Since upgrade from 43 to 44, Firefox crashes with message "reordered frames present."

  • 1 பதிலளி
  • 1 இந்த பிரச்சனை உள்ளது
  • 20 views
  • Last reply by gldearman

I am currently running Firefox 44.0.1 on Ubuntu 12.04.

When I first updated to 43, any HTML5 embedded video caused a crash. I fixed that by changing media.fragmented-mp4.ffmpeg.enabled to "false." From then on, everything went fine until I updated to 44 yesterday.

Now the crashes are back. Any time there is an HTML5 embedded video, the browser crashes. This is true even if the video doesn't play — I have media.autoplay.enabled set to "false." But if I so much as scroll down my facebook feed, the browser crashes as soon as I reach a video. The browser is crashing constantly, to the point of unusability.

The error message output to the command line references h.264, and says "reordered frames present."

I've started in safe mode — same problem. Started with a brand-new profile — same problem. With a brand-new profile in safe mode — same problem. The crashes occur whether or not the OpenH264 plugin by Cisco is enabled or disabled. I've searched about:config for any other "media.fragmented*" parameters, but there are none except the one I mention above.

Any help would be greatly appreciated.

Thanks!

I am currently running Firefox 44.0.1 on Ubuntu 12.04. When I first updated to 43, any HTML5 embedded video caused a crash. I fixed that by changing media.fragmented-mp4.ffmpeg.enabled to "false." From then on, everything went fine until I updated to 44 yesterday. Now the crashes are back. Any time there is an HTML5 embedded video, the browser crashes. This is true even if the video doesn't play — I have media.autoplay.enabled set to "false." But if I so much as scroll down my facebook feed, the browser crashes as soon as I reach a video. The browser is crashing constantly, to the point of unusability. The error message output to the command line references h.264, and says "reordered frames present." I've started in safe mode — same problem. Started with a brand-new profile — same problem. With a brand-new profile in safe mode — same problem. The crashes occur whether or not the OpenH264 plugin by Cisco is enabled or disabled. I've searched about:config for any other "media.fragmented*" parameters, but there are none except the one I mention above. Any help would be greatly appreciated. Thanks!

All Replies (1)

I updated to 44.0.2 this morning. Still crashing, but the crashes are behaving slightly differently.

Here are my crash reports from today: bp-0ad8caf4-60be-45f5-a803-3c8c92160212 bp-118ad077-dff1-49a5-a266-49dc92160212 bp-69ad5310-d46a-4b05-aa0f-379c52160212 bp-379fbabb-e989-4023-b691-dd2ab2160212 bp-edd48a22-bd37-41e5-8025-7f6302160212 bp-572c0fce-1b12-4d81-8ccf-0e5582160212

Firefox just crashed while I was trying to type this message with no other pages open, so the crashes seem to not be always linked to embedded video. I no longer get a "reordered frames present" error message at the prompt when the browser crashes (with one exception, see below).

I can now visit a page with an embedded video without crashing immediately. However, attempting to play that video causes an immediate crash.

I've found two pages with embedded videos that behaves differently (but still cause a crash). I try to play the video at this HTML5 video test page, I get a segmentation fault error, the core dumps, Firefox crashes, and the Crash Reporter does not run, so no crash report is submitted. I can visit the page without a problem, until I try to play the video.

The other page I've found that behaves differently is the Twitter home page. If I try to scroll down there, without clicking anything, Firefox crashes. Unlike other crashes since the 44.0.2 upgrade, I still get the message "reordered frames are present" and a message that h264 is "increasing reorder buffer to 1."

I hope someone can help me with this before I give up and downgrade to Firefox 42.