New issue
Advanced search Search tips

Issue 761339 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Previous locations:
webrtc:8186


Sign in to add a comment

Probability,once chrome received video stream,the tab page crashes on M58

Reported by 931563...@qq.com, Aug 31 2017

Issue description

What steps will reproduce the problem?
1.Audio codec is opus and video codec is h264
2.chrome receives video stream
What is the expected result?
Chrome send and receive audio and video streams normally and video can play normally.

What do you see instead?
Probability (about one percent to five percents),once chrome received video stream,the remote video is still,the tab page is also still , all the buttons have no response。Browser stops sending and receiving audio and video streams. After about one minute,the tab page crashes. If I open a new tab page,it is OK.

I test on M57,M59,M60,the problem has not appeared yet.


What version of the product are you using? On what operating system?
M58,windows7

Please provide any additional information below.
log of chrome
WARNING	4340	5920	19:31:40-832	c:\b\build\slave\win-pgo\build\src\third_party\webkit\source\core\html\htmlmediaelement.cpp	1995	currentPlaybackPosition readyState = 4 but no webMeidaPlayer to provide currentPlaybackPosition
WARNING	4340	5920	19:31:40-833	c:\b\build\slave\win-pgo\build\src\third_party\webkit\source\core\html\htmlmediaelement.cpp	1995	currentPlaybackPosition readyState = 4 but no webMeidaPlayer to provide currentPlaybackPosition
WARNING	4340	6224	19:31:41-293	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\modules\bitrate_controller\bitrate_controller_impl.cc	68	Received report block where extended high sequence number goes backwards, ignoring.
ERROR	4340	6224	19:31:41-296	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\p2p\base\dtlstransportchannel.cc	534	Jingle:DtlsTransport[video|1|_W]: Received unexpected non-DTLS packet.
INFORMATION	6940	6912	19:31:41-366	CONSOLE	3403	"DEBUG: [2017-08-22 19:31:41]", source: https://189.195.101.82/webrtc/main.444feda5.js (3403)
INFORMATION	6940	6912	19:31:41-366	CONSOLE	3403	"INFO: [2017-08-22 19:31:41]", source: https://189.195.101.82/webrtc/main.444feda5.js (3403)
ERROR	4340	6224	19:31:42-293	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\p2p\base\dtlstransportchannel.cc	534	Jingle:DtlsTransport[video|1|_W]: Received unexpected non-DTLS packet.
ERROR	4340	6224	19:31:43-298	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\p2p\base\dtlstransportchannel.cc	534	Jingle:DtlsTransport[video|1|_W]: Received unexpected non-DTLS packet.
WARNING	6940	7068	19:31:45-225	c:\b\build\slave\win-pgo\build\src\net\dns\dns_config_service_win.cc	661	Failed to read DnsConfig.
WARNING	4340	4716	19:31:46-299	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\modules\rtp_rtcp\source\rtp_rtcp_impl.cc	168	webrtc::ModuleRtpRtcpImpl::Process: Timeout: No RTCP RR received.
WARNING	4340	4716	19:31:46-304	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\modules\rtp_rtcp\source\rtp_rtcp_impl.cc	170	webrtc::ModuleRtpRtcpImpl::Process: Timeout: No increase in RTCP RR extended highest sequence number.
WARNING	4340	3364	19:31:46-940	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\video\video_receive_stream.cc	487	No decodable frame in 3000 ms, requesting keyframe.
WARNING	4340	3364	19:31:49-940	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\video\video_receive_stream.cc	487	No decodable frame in 3000 ms, requesting keyframe.
WARNING	6940	7068	19:31:50-227	c:\b\build\slave\win-pgo\build\src\net\dns\dns_config_service_win.cc	661	Failed to read DnsConfig.
WARNING	4340	3364	19:31:52-940	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\video\video_receive_stream.cc	487	No decodable frame in 3000 ms, requesting keyframe.
WARNING	6940	7068	19:31:55-230	c:\b\build\slave\win-pgo\build\src\net\dns\dns_config_service_win.cc	661	Failed to read DnsConfig.
WARNING	4340	3364	19:31:55-940	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\video\video_receive_stream.cc	487	No decodable frame in 3000 ms, requesting keyframe.
WARNING	4340	5012	19:31:58-298	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\modules\rtp_rtcp\source\rtp_rtcp_impl.cc	168	webrtc::ModuleRtpRtcpImpl::Process: Timeout: No RTCP RR received.
WARNING	4340	5012	19:31:58-303	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\modules\rtp_rtcp\source\rtp_rtcp_impl.cc	170	webrtc::ModuleRtpRtcpImpl::Process: Timeout: No increase in RTCP RR extended highest sequence number.
WARNING	4340	3364	19:31:58-940	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\video\video_receive_stream.cc	487	No decodable frame in 3000 ms, requesting keyframe.
WARNING	6940	7068	19:32:00-232	c:\b\build\slave\win-pgo\build\src\net\dns\dns_config_service_win.cc	661	Failed to read DnsConfig.
WARNING	4340	3364	19:32:01-940	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\video\video_receive_stream.cc	487	No decodable frame in 3000 ms, requesting keyframe.
WARNING	4340	3364	19:32:04-941	c:\b\build\slave\win-pgo\build\src\third_party\webrtc\video\video_receive_stream.cc	487	No decodable frame in 3000 ms, requesting keyframe.
WARNING	6940	7068	19:32:05-234	c:\b\build\slave\win-pgo\build\src\net\dns\dns_config_service_win.cc	661	Failed to read DnsConfig.


 

Comment 1 Deleted

Comment 2 by 931563...@qq.com, Aug 31 2017

I find similar issue https://bugs.chromium.org/p/webrtc/issues/detail?id=7505

my crash id:78b82295-8f62-45b2-935d-8d774410b41e

Can you please help me to confirm is the reason of my problem the same with this issue?
Project: chromium
Moved issue webrtc:8186 to now be  issue chromium:761339 .
Cc: jmukthavaram@chromium.org
Labels: Needs-Milestone Needs-Feedback
931563694@,
Thanks for filing the issue.

Could you please check the issue by upgrading chrome to the latest chrome stable#61.0.3163.79 & latest Canary#63.0.3208.0. If still issue persists, please  provide us the sample URL  and screencast where exactly you observed the issue.


Status: WontFix (was: Unconfirmed)
Due to lack of user feedback closing this issue.
Please feel free to raise a new issue if you face any issue on chrome further.
Thanks..!

Sign in to add a comment