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

Issue 590520 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Feb 2016
Cc:
█ cbentzel@chromium.org
chrome-perf-bugs@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Performance issue:

Reported by terki...@gmail.com, Feb 28 2016 
Chrome Version       : 48.0.2564.116-132.2.x86_64
Operating System and Version: openSUSE 13.1 3.11.10-7-default
URLs (if applicable) : <null>

Description of performance problem: multiple chromium pid's with high cpu time, rendering chromium unusable



Remember to attach your trace file to this bug!
trace_Sun_Feb_28_2016_14.51.47.json.rar
7.1 MB Download

Comment 1 by terki...@gmail.com, Feb 28 2016 

Reboot seems to corrected the situtation to normal.
Before the problem started laptop was connected with HDMI to tv.
Probably a distribution, DE environment, audio backend problem etc.

Comment 2 by ssamanoori@chromium.org, Feb 29 2016

Labels: Needs-Feedback
terkir81@Could you please confirm whether this issue can be closed as per comment #1?

Comment 3 by rsch...@chromium.org, Feb 29 2016

Cc: cbentzel@chromium.org
The first thing I notice about the trace is the very long network activity, with huge SOCKET_IN_USE blocks. +cbentzel do you know what's going on here?

The second thing I notice is that a lot of the CPU time is descheduled. terkir81, what kind of CPU is on this machine? Was there a lot of CPU activity from anything besides Chrome?

Comment 4 by terki...@gmail.com, Feb 29 2016 

"terkir81@Could you please confirm whether this issue can be closed as per comment #1?"
Yes, this can be closed. After reboot everything seems to be normal.

Answer to Comment#3
CPU is Intel Pentium CPU B940 @ 2.00GHz
machine ProBook 4530s
vaapi-intel-driver-1.6.99-1.1.x86_64

Beside Chromium there was maybe a kmail, akregator running. So not much cpu activity besides Chromium. Other persona in Chromium was not running or wasn't visibly active.

Comment 5 by cbentzel@chromium.org, Feb 29 2016 

SOCKET_IN_USE is typically due to us limiting to 6 sockets per host on HTTP/1.1 connections. If there are 6 active requests to a host still going on, new requests will stall while waiting for them to complete.

Comment 6 by cbentzel@chromium.org, Feb 29 2016

Status: WontFix (was: Unconfirmed)
Closed per comment #4
►

Sign in to add a comment