RESOLVED FIXED 169727
Improve WebRTC track enabled support
https://bugs.webkit.org/show_bug.cgi?id=169727
Summary Improve WebRTC track enabled support
youenn fablet
Reported 2017-03-15 17:36:22 PDT
These tests could be improved a bit and made more clear why they fail.
Attachments
Patch (32.28 KB, patch)
2017-03-15 21:59 PDT, youenn fablet
no flags
Patch (32.14 KB, patch)
2017-03-15 22:02 PDT, youenn fablet
no flags
Patch for landing (32.19 KB, patch)
2017-03-16 08:28 PDT, youenn fablet
no flags
youenn fablet
Comment 1 2017-03-15 21:59:36 PDT
youenn fablet
Comment 2 2017-03-15 22:01:21 PDT
This is a first step. If we follow that direction, we might want to handle that at RealtimeMediaSource level, so that it generates the black frame/silence in videoSampleAvailable/audioSamplesAvailable
youenn fablet
Comment 3 2017-03-15 22:02:14 PDT
Alex Christensen
Comment 4 2017-03-16 00:34:03 PDT
Comment on attachment 304608 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=304608&action=review > Source/WebCore/ChangeLog:12 > + Mkaking sure muted/disabled sources produce silence/black frames. Making > Source/WebCore/ChangeLog:24 > + (WebCore::RealtimeIncomingVideoSource::pixelBufferFromVideoFrame):i Generating black frames if muted. i > Source/WebCore/platform/mediastream/mac/RealtimeIncomingVideoSource.cpp:100 > + auto status = CVPixelBufferCreate(kCFAllocatorDefault, frame.width(), frame.height(), kCVPixelFormatType_420YpCbCr8Planar, nullptr, &pixelBuffer); This looks like a memory leak. What deallocates this? We should probably return a smart pointer type. > Source/WebCore/platform/mediastream/mac/RealtimeIncomingVideoSource.cpp:104 > + ASSERT(!status); Does status of 0 have a name?
youenn fablet
Comment 5 2017-03-16 08:28:54 PDT
Created attachment 304641 [details] Patch for landing
youenn fablet
Comment 6 2017-03-16 08:32:17 PDT
Thanks for the review (In reply to comment #4) > Comment on attachment 304608 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=304608&action=review > > > Source/WebCore/ChangeLog:12 > > + Mkaking sure muted/disabled sources produce silence/black frames. > > Making OK > > > Source/WebCore/ChangeLog:24 > > + (WebCore::RealtimeIncomingVideoSource::pixelBufferFromVideoFrame):i Generating black frames if muted. > > i OK > > > Source/WebCore/platform/mediastream/mac/RealtimeIncomingVideoSource.cpp:100 > > + auto status = CVPixelBufferCreate(kCFAllocatorDefault, frame.width(), frame.height(), kCVPixelFormatType_420YpCbCr8Planar, nullptr, &pixelBuffer); > > This looks like a memory leak. What deallocates this? We should probably > return a smart pointer type. pixelBuffer is retained by m_blackFrame. I put the assignment closer to the allocation. > > > Source/WebCore/platform/mediastream/mac/RealtimeIncomingVideoSource.cpp:104 > > + ASSERT(!status); > > Does status of 0 have a name? Changed to noErr.
WebKit Commit Bot
Comment 7 2017-03-16 09:09:54 PDT
Comment on attachment 304641 [details] Patch for landing Clearing flags on attachment: 304641 Committed r214044: <http://trac.webkit.org/changeset/214044>
WebKit Commit Bot
Comment 8 2017-03-16 09:09:58 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.