Getting 100% CPU
Reported by
tatvasof...@gmail.com,
Jun 13 2017
|
||||||||||||||||
Issue descriptionWhat steps will reproduce the problem? 1.https://webrtc.github.io/samples/src/content/peerconnection/multiple/ 2.Start 3.Call What is the expected result? Should initiate call with normal CPU usage, 40-50%. What do you see instead? 100% CPU usage. What version of the product are you using? On what operating system? -Windows 7 Professional Service Pack 1 -Intel Core 2 Duo , 2.20 GHz -2 GB RAM Please provide any additional information below.
,
Jun 13 2017
This issue reproduce with 2 GB RAM only. It is working fine with 4 GB and higher RAM.
,
Jun 16 2017
,
Jun 16 2017
,
Jun 22 2017
,
Jun 22 2017
deadbeef@: Can you take a look at this? If you think this issue is caused by the blink/content side of things, please bounce back to the PeerConnection component.
,
Jun 22 2017
,
Jun 25 2017
,
Jun 27 2017
As per comment#2, issue is reproducable only with 2GB RAM. As we (chrome-hyd team)do not have Windows7 with 2GB RAM machine to check this issue,adding 'TE-Hardware-Dependency' label to this issue. Thanks..!!
,
Jul 11 2017
Anatoli, can you help triage this? What do we typically do with performance issues?
,
Jul 11 2017
tatvasoft154@ Can you also post a screenshot of the Processes tab in the task manager? What version of Chrome are you using? Do you get the same result with other samples or only with the PeerConnection sample?
,
Aug 8 2017
I am using Chrome Version 47.0.2526.73 m (64-bit). Do you get the same result with other samples or only with the PeerConnection sample? => With other samples also the CPU utilization is high I have checked with "Peer connection" demo, the CPU usage goes to 90+ percent. I have attached screenshot for it (cpuuseage_peerconnection.jpg). For "Multiple peer connections" demo CPU utilization is 100 percent constant (cpuuseage_multiple.jpg).
,
Aug 8 2017
Thank you for providing more feedback. Adding requester "anatolid@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
,
Aug 9 2017
tatvasoft154@: Chrome 47 is too old for this to be actionable. Can you try with a more recent version? The current stable version is 60. If you try with Dev or Canary, that would be even better.
,
Aug 10 2017
I have tested with chrome version 60.0.3112.90 (Official Build) (64-bit) and I am getting same issue.
,
Aug 10 2017
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
,
Sep 7 2017
,
Sep 7 2017
,
Jan 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 16
Archiving old issue. Please file a new bug or reopen if this is still an issue. |
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
Comment 1 by tatvasof...@gmail.com
, Jun 13 2017526 KB
526 KB View Download