SourceBuffer of MSE does freeze in updating state

Duplicate Issue #8312714 • See Issue #13951005


Jul 28, 2016
This issue is public.
Found in
  • Internet Explorer
Standard affected
Media Source Extensions

See progress on Bug #13951005
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

The following issue occurs in IE11 on Windows 8.

Wrap an MP3 into an MP4 file with MP4Box and segment it afterwards.

mp4box -add any-mp3.mp3#audio unsegmented.m4a
mp4box -dash 10000 -frag 1000 unsegmented.m4a

This will create a file named unsegmented_dashinit.mp4. If this MP4 file gets added to a SourceBuffer of a MediaSource, this SourceBuffer will transition to its updating state. It will then never fire an error or updateend event again. It will just remain in the updating state forever.

Please tell me if you need more details to reproduce the issue.


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Status to “Won’t fix”

    • Based on recent testing the issue has been fixed and will
      be closed out to reflect this. Should you happen to see the problem as still
      active in Win 10  / MS Edge please feel free to activate the feedback and

      Please note that we are not working on IE feature bugs any
      longer at this time unless they are security related.

      All the best,
      The MS Edge Team

    • Hi Brad, many thanks for having a look at this issue.

      I ran my test case again today in Edge 14 (14393 via the official VirtualBox image from on Windows 10 and it still behaves the same. The SourceBuffer doesn’t fire any event after transitioning to its updating state.

      Could you please take a look at it again?

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Status from “Won’t fix”

      Changed Assigned To from “Brad E.” to “James M.”

      Changed Status to “Duplicate”

    • Hello,

      Thank you for providing this information about the issue. We are currently working on this problem for a future release of Edge, and we will post further updates on issue ticket #8972303.

      Best Wishes,
      The MS Edge Team

    • This bug has marked as duplicate. Please follow the parent issue to get new updates.

    You need to sign in to your Microsoft account to add a comment.

    Sign in