Closed
Bug 789705
Opened 13 years ago
Closed 13 years ago
canvas.drawImage using the output of getUserMedia sometimes fails with "Component not available"
Categories
(Core :: WebRTC: Audio/Video, defect)
Core
WebRTC: Audio/Video
Tracking
()
RESOLVED
INVALID
People
(Reporter: derf, Unassigned)
References
()
Details
(Whiteboard: [getUserMedia], [blocking-gum+])
canvas.drawImage using the output of getUserMedia run through a video tag sometimes fails with "Component not available". This happens very often on anant's Mac, and rarely on my Linux machine, so I suspect some kind of race condition. According to Bas, this can only happen if nsLayoutUtils::SurfaceFromElement() fails with some reason _other_ than mIsStillLoading==true. Possibly this is related to bug 771833?
Reproducible test case:
Comment 1•13 years ago
|
||
Related to bug 778682?
Updated•13 years ago
|
Whiteboard: [getUserMedia] → [getUserMedia], [blocking-gum+]
This demo doesn't have any code ensuring that video frames have actually arrived at the <video> element after setting video.src = stream.
The demo could wait for a "canplaythrough" event before it starts doing its drawImage(). Or, once I've fixed bug 778682, the demo could wait for a "loadeddata" event.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Comment 3•13 years ago
|
||
Why was this closed as invalid?
Reporter | ||
Comment 4•13 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #3)
> Why was this closed as invalid?
I presume because the bug was in the demo (see comment 2). It could also conceivably have been duped to bug 778682.
Comment 5•13 years ago
|
||
yes
You need to log in
before you can comment on or make changes to this bug.
Description
•