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

Issue 803805 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 24
Cc:
█ sandeepkumars@chromium.org
█ viswatej...@techmahindra.com
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

High CPU Utilization on Windows RDS

Reported by supp...@microbyte.co.uk, Jan 19 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Use chrome
2. 
3. 

What is the expected behavior?
The servers suddenly run slowly.

On further investigation the CPU is at 99% and there are lots or instances or chrome running causing this.

What went wrong?

On further investigation the CPU is at 99% and there are lots or instances or chrome running causing this.

The issue is intermittent and effects all users at random.

we have a number of customer with this similar issue

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 10.0
Flash Version: .

Comment 1 by viswatej...@techmahindra.com, Jan 23 2018 

As the ET team doesn't have Remote Desktop set up to test and confirm this issue, forwarding this to inhouse team for further triaging it, hence adding TE-NeedsTriageFromHYD, could anyone from the inhouse team have a look at this issue.

Thanks!

Comment 2 by sc00335...@techmahindra.com, Jan 23 2018

Cc: viswatej...@techmahindra.com
Labels: Triaged-ET TE-NeedsTriageFromHYD Needs-Triage-M63

Comment 3 by supp...@microbyte.co.uk, Jan 25 2018 

Thank you - any idea on a time frame for an update?

Comment 4 by sandeepkumars@chromium.org, Feb 2 2018

Cc: sandeepkumars@chromium.org
Labels: Needs-Feedback
@Reporter: The latest Stable update #64.0.3282.140 version is available now. Could you please check the issue is latest and update?

Thanks!!

Comment 5 by dtapu...@chromium.org, Jul 24

Status: WontFix (was: Unconfirmed)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.
►

Sign in to add a comment