New issue
Advanced search Search tips

Issue 900115 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:'Screencastify' extension failed to record and Error 'Fail to start recording' is seen while recording.

Reported by shruti.j...@etouch.net, Oct 30

Issue description

Chrome Version : 72.0.3595.2 (Official Build) 4af8b5a14fa87ad1e81fa9ae20c30f9a8c1494cb-refs/branch-heads/3595@{#4} 32/64 bit
OS : Mac(10.13.1, 10.13.6, 10.14.1), Windows(7,8,10), Linux(14.04 LTS)

Test URL:https://chrome.google.com/webstore/detail/screencastify-screen-vide/mmeijimgabbpbgpdklnllpncmdofkcpn/related?utm_source=chrome-ntp-icon

Steps to reproduce:
1. Launch chrome and download the extension from given test URL.
2. Login with valid credentials.
3. Click on extension icon for recording ,select browser for recording.
4. Observe.

Actual Result: 'Screencastify' extension failed to record and Error 'Fail to start recording' is seen while recording.
Expected Result :Recording should be successful using 'Screencastify' extension.

This is a regression issue broken in ‘M-71’ and will soon inform the bisect info:
Good Build :71.0.3548.0 
Bad Build  :71.0.3549.0 

Kindly refer the attached screen-cast.
Thank you..!
 
Actual_result.mov
6.1 MB View Download
Expected_result.mov
11.2 MB View Download
Cc: battre@chromium.org
Labels: hasbisect
Owner: sprang@chromium.org
Status: Assigned (was: Unconfirmed)
Update:
Bisect info:

You are probably looking for a change made after 589868 (known good), but no later than 589885 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/771206507ab469fe7a382befcf273c42ef3cc702..a9d73d33ae5744456aece5cb170b802a77451462
Suspect:https://chromium.googlesource.com/chromium/src/+/6498431e2138bed86d4f8c5ba5bba60e10498ef2

@Erik Språng: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.


Note:

1.Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message.
2.Tried on other machines but still getting the same error again.
3.Hence provided suspect through 'Chromium bisect'.

Thank you..!

Labels: ReleaseBlock-Stable
Adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!
Cc: sprang@chromium.org
Owner: mcasas@chromium.org
The change I did only affects chromeos, so that's not it.
I'm guessing this has something to do with media recorder api?
mcasas@ can you triage?
M71 Stable promotion is coming VERY soon. Your bug is labelled as Stable  ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.
Cc: guidou@chromium.org
Components: Blink>MediaStream
Labels: Needs-Feedback
I'd say this is due to
 Remove deprecated URL.createObjectURL(MediaStream) [1]

which changes the usual way of plugging a MediaStream to a <video>
from the old 
 video.src = URL.createObjectURL(mediaStream)
to
 video.srcObject = mediaStream
see [2].

It also broke some (all?) of my demos and expect those that aren't 
actively maintained to be broken.

shruti.jadhav@ could you please confirm? If this is the case, then
this is not a regression nor a ReleaesBlocker.


[1] https://chromium.googlesource.com/chromium/src/+/d38023cc2b6816e5c2d5d4f1d290306de3d01a70
[2] https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/tWzutytXsqc/lGaWCFdHAgAJ
M71 Stable promotion is coming VERY soon. Your bug is labelled as Stable  ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.
Labels: -Pri-1 -ReleaseBlock-Stable Pri-2
Owner: guidou@chromium.org
This is not a release blocker, since all other extensions are 
working and I have a hunch that an unrelated API deprecation is
the culprit for this.
Status: WontFix (was: Assigned)
I tried the extension and it works well on ToT and on the suspect range.
I am assuming it was the issue mentioned in #5 and that it was already fixed.

Please reopen if this is incorrect.

Sign in to add a comment