[Webkit-unassigned] [Bug 215005] New: [GTK][WPE][WebRTC] webrtc/h264-baseline.html is crashing since added in r265005
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jul 30 21:09:12 PDT 2020
https://bugs.webkit.org/show_bug.cgi?id=215005
Bug ID: 215005
Summary: [GTK][WPE][WebRTC] webrtc/h264-baseline.html is
crashing since added in r265005
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebRTC
Assignee: webkit-unassigned at lists.webkit.org
Reporter: lmoura at igalia.com
CC: youennf at gmail.com
* webrtc/h264-baseline.html
It is crashing in the WebProcess since added in r265005. Stderr from debug run:
crash log for WebKitTestRunner (pid 8249):
STDERR: (used_ids.h:55): Duplicate id found. Reassigning from 1 to 14
STDERR: (used_ids.h:55): Duplicate id found. Reassigning from 3 to 13
STDERR: (used_ids.h:55): Duplicate id found. Reassigning from 5 to 12
STDERR: (used_ids.h:55): Duplicate id found. Reassigning from 6 to 11
STDERR: (webrtc_video_engine.cc:3160): Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
STDERR: (webrtc_video_engine.cc:2008): RTX SSRCs configured but there's no configured RTX payload type. Ignoring.
STDERR: (balanced_degradation_settings.cc:96): Unsupported size, value ignored.
STDERR: (video_send_stream_impl.cc:243): ERROR: Initial encoder max bitrate = -1 which is <= 0!
STDERR: (video_stream_encoder.cc:1274): Failed to encode frame. Error code: -1
STDERR: (video_receive_stream.cc:721): No decodable frame in 200 ms, requesting keyframe.
STDERR:
STDERR:
STDERR: #
STDERR: # Fatal error in: ../../Source/ThirdParty/libwebrtc/Source/webrtc/modules/rtp_rtcp/source/rtp_format_h264.cc, line 189
STDERR: # last system error: 110
STDERR: # Check failed: fragment.size() > 0 (0 vs. 0)
STDERR: # #CRASHED - WebKitWebProcess (pid 8316)
STDERR: LEAK: 1 WebProcessPool
STDERR: LEAK: 1 WebPageProxy
Crashes always happens when "counter" reaches 7 in waitForVideoSize, otherwise just rejects as failure. Maybe because some cleanup timer trigger a process crash instead of an actual crash?
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200731/666b1e8a/attachment.htm>
More information about the webkit-unassigned
mailing list