Issue metadata
Sign in to add a comment
|
navigator.mediaDevices.getUserMedia() crashes extensions in Chrome v59
Reported by
hoboman...@gmail.com,
Jun 18 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36
Steps to reproduce the problem:
I'm using Chrome's chrome.desktopCapture.chooseDesktopMedia() to get a user's audio and video streamId before passing it to navigator.mediaDevices.getUserMedia() like so:
navigator.mediaDevices.getUserMedia({
audio: {
optional: {
chromeMediaSource: 'desktop',
chromeMediaSourceId
}
},
video: {
optional: {
chromeMediaSource: 'desktop',
chromeMediaSourceId
}
}
})
In Chrome v58, this worked perfectly, but with version v59 this causes the extension to crash.
To reproduce:
1. Get https://chrome.google.com/webstore/detail/screen-recorder/gdamcnkmddbfhaadidkhahllkabienpk (not my personal extension, but same premise)
2. Try recording your screen with audio enabled.
3. See the app crash.
Attached is a dump file of the crash.
What is the expected behavior?
No crash.
What went wrong?
The extension crashes and needs to be reloaded.
WebStore page: https://chrome.google.com/webstore/detail/screen-recorder/gdamcnkmddbfhaadidkhahllkabienpk
Did this work before? Yes
Chrome version: 59.0.3071.104 Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 26.0 r0
,
Jun 19 2017
Unable to reproduce this issue on Windows-10 using chrome latest stable #59.0.3071.104 by following steps mentioned in the original comment. No crashes observed while recording the video by enabling the audio. Reporter@ Are you able to reproduce this issue consistently including incognito mode? If yes, please provide crash ID's from chrome://crashes for further investigation. Thanks!
,
Jun 19 2017
I am able to reproduce it consistently and in incognito. Crash ID 03df3913-a67f-47ba-8f45-6387d8e01d25
,
Jun 19 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 19 2017
Please provide the crash report ID as well, Attaching the sample screenshot below for reference.
,
Jun 19 2017
I don't know anything about the report ID and it doesn't look like one is created for me here. The bolded crash id is the one I mentioned above.
,
Jun 19 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 20 2017
As per the provided screen-shot in comment #6 I can see one crash ID: 1c9113ee40000000. Could you please confirm is this crash is related to the same issue or different issue. Thanks!
,
Jun 20 2017
Can confirm. It is it.
,
Jun 20 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 21 2017
Stack trace of the above Crash I'd looks similar to issue 714447. Hence merging this issue into 714447, undo if not the case. Thanks!! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Jun 19 2017