Guys, reporting a bug here is a pain in the ass, I tried to submit report 4 times and now the attached demo is missing. Where is it?
Attaching again...

Deleted: chrome-recorder.zip 5.4 KB

chrome-recorder.zip 5.4 KB Download

This issue looks similar to the issue id: 606000. Hence, merging into the issue id: 606000.

Thanks...!!

Hi, please consider splitting issues again because both bugs are different.
I'm still having the same issue!

#4: demian85: first please read [1] :-)
and with that in hand, please try the potential bug in the description
with the latest Canary, and paying attention to the comments in [2]
re. SourceBuffer.busy flag. (I can see that the .busy behaviour is 
a bit counterintuitive, but I'm afraid that's an issue with the 
Spec [3]).

If your error is still present, then it's not a duplicate, we'll de-dup
it and investigate.  As usual, providing the tiniest use case to
repro is the surest way for a fix (which you can also code yourself
and upload for review).


[1] https://bugs.chromium.org/p/chromium/issues/detail?id=606000#c84
[2] https://bugs.chromium.org/p/chromium/issues/detail?id=606000#c50
[3] https://www.w3.org/TR/media-source/

Okay, I understand. But I'm only asking for directions on where to find the
respective patches so I can submit them to Electron for evaluation.
The patch that I mentioned before has been accepted because I provided a
demo to reproduce the bug.
Unfortunately, problem didn't seem to go away, so it's a possibility that
many other changes after M54 somehow fixed this issue in latest Canary.

Thanks.

Unfortunately its very hard to speculate what change make the difference between these two milestones - there are tons of changes. My best guess (no promises):
https://codereview.chromium.org/2343543002/

You might try forking Electron and just rolling it forward to 56. Sorry, I know thats not easy. 

One other thing you might try is using plain <video src=stream> rather than MSE. You can see a demo of this here:

https://storage.googleapis.com/chcunningham-chrome-shared/mr_to_mse.html?enable_src_eq=true

(note the arg to enable_src_eq=true. clear your cache if its not working - I've just uploaded a new version)

I find that the src=stream approach works in current chromium stable and may work in electron as well

I'm not sure what you are suggesting. How can I use 'src' video attribute
to feed video chunks instead of MSE? I don't have a single video file, I
have many video chunks!
Your demo prints warnings on Chrome 56 stating that "MSE has gaps" and
video feed gets stuck sometimes, however it plays fine on Chrome Canary.

The demo I linked has two <video> tags. The one on the left (under SRC=) does not use MSE. Instead the video is wired directly to the recording stream with this code:

srcEqVideo.src = (window.URL || window.webkitURL).createObjectURL(stream);

Take a look at the surrounding javascript. Perhaps you can pipe your stream directly into the video tag in a similar fashion. 

The video tag on the right uses MSE and will not work reliably until M58 ships to stable. 

Unfortunately that's not my use case. I have a desktop app, so one user
records screen with MR and other consumes the video chunks with MSE...
So are you completely sure that M58 is needed for this to work?
I may loose my job if I cannot make this work on Electron.
Thanks anyway.