Make sure that if the RTCPeerConnectionHandler can't be fully initialized let the RTCPeerConnection constructor throw an exception.
Created attachment 168680 [details] Patch
Created attachment 169111 [details] Patch
Comment on attachment 169111 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=169111&action=review > Source/WebCore/platform/mediastream/chromium/RTCPeerConnectionHandlerChromium.cpp:71 > + return adoptPtr<RTCPeerConnectionHandler>(0); You can just return nullptr (or at least PassOwnPtr<RTCPeerConnectionHandler>() if that doesn't work).
Created attachment 169370 [details] Patch for landing
Created attachment 169371 [details] Patch for landing
(In reply to comment #3) > (From update of attachment 169111 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=169111&action=review > > > Source/WebCore/platform/mediastream/chromium/RTCPeerConnectionHandlerChromium.cpp:71 > > + return adoptPtr<RTCPeerConnectionHandler>(0); > > You can just return nullptr (or at least PassOwnPtr<RTCPeerConnectionHandler>() if that doesn't work). Ahh, that's the reason the old return 0; doesn't work anymore. Nice.
Comment on attachment 169371 [details] Patch for landing Clearing flags on attachment: 169371 Committed r131721: <http://trac.webkit.org/changeset/131721>