New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 781232 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

Performance issue:

Reported by stephane...@gmail.com, Nov 3 2017

Issue description

Chrome Version       : 62.0.3202.75
Operating System and Version: 6.1.7601 SP1
URLs (if applicable) :

Description of performance problem:
Chrome is not responding during the first call received with webrtc. Once the call hangs up, Chrome recovers and the next call in is fine. I attached the trace with both calls. 



Remember to attach your trace file to this bug!

 
trace_Answer2nd.json.gz
7.6 MB Download
Components: Blink>WebRTC
Labels: Needs-Feedback
Can you provide more specific reproduction steps and more details about the OS/Chrome versions involved?
Chrome version was on both 61 and 62.0.3202.75. It is Windows 7 SP1 OS. 
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 5 2017

Cc: guidou@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "guidou@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Can you provide more specific reproduction steps?
For example, a URL where the problem can be reproduced.
unfortunately the URL is internal and not exposed to the internet. I was wondering if there is anything in the trace that may give us a clue about what could be causing Chrome to hang. 

Project Member

Comment 7 by sheriffbot@chromium.org, Nov 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "guidou@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
If this is something that used to work in the past, maybe you can use the bisect script to find which change caused the regression. See http://www.chromium.org/developers/bisect-builds-py


no this is a new feature we introduced in our environment. 
Project Member

Comment 10 by sheriffbot@chromium.org, Nov 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "guidou@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
Closing this bug since it is not actionable on the Chromium side.
Please reopen once you can provide reproduction steps that we can use to diagnose the problem.

Sign in to add a comment