Chrome is hogging open files |
|||||
Issue descriptionChrome Version : 62.0.3202.62 OS Version: OS X 10.12.6 What steps will reproduce the problem? 1. Open Chrome with two profile windows, each with a handful of tabs (I had 17 tabs in one profile, 11 tabs int he other) 2. Inspect the open files Chrome is using via `lsof` What is the expected result? You expect it to be a sane number. What happens instead of that? $ lsof|cut -d' ' -f1|sort|uniq -c|sort|tail -n 10 271 profiled 274 passd 277 sharingd 290 ServerFil 326 searchd 499 UserEvent 528 ARDAgent 545 SpringBoa 637 com.apple 2481 Google Chrome them seemingly leaks open files, because this number grows to over 3,600 on my system, at which time all processes start breaking because there are no more open files. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36
,
Oct 19 2017
I'd suspect the cache. Cache folks, any ideas here?
,
Oct 20 2017
Are you sure they're all Chrome? On my corp Mac, I have 509 lsof results starting with "Google", but only 92 of them have "Google Chrome". Admittedly, just have one tab open at the ntp, but should make sure that this is a Chrome issue.
,
Oct 20 2017
Yep: (14415) 09:46 AM - ~ $ lsof|cut -d' ' -f1|sort|uniq -c|sort|grep Google 3218 Google ## Then I shut down Chrome (14416) 09:46 AM - ~ $ lsof|cut -d' ' -f1|sort|uniq -c|sort|grep Google (14417) 09:47 AM - ~ $
,
Oct 20 2017
Also, in case it's relevant, I have an open CRD session as well.
,
Oct 23 2017
Any sense of how these files are named? (Kinda tricky to ask concretely since there may be privacy implications).
,
Oct 23 2017
$ lsof|grep -E '^Google'|tr -s ' '|cut -d' ' -f9-|sort|uniq -c|sort https://gist.github.com/tvolkert/9b73c3d3d2dfc401191fee8fd9acb215
,
Oct 23 2017
Huh, nothing in particular stands out there, except for # of opens on icu stuff at the end, but that may have to do with number of processes? Any idea on what's up with the last line?
,
Oct 23 2017
Here goes... $ lsof|grep -E '^Google'|tr -s ' '|while read l; do f=$(echo "$l"|cut -d' ' -f9-); if [[ -z "$f" ]]; then echo $l; fi; done https://gist.github.com/tvolkert/a6afbb69d8cc7617f6071bcc53a51814 Different question from the output of comment #7: why are there seemingly 94 processes when I only have 28 tabs open?
,
Oct 24 2017
So some RPC stuff? Not really familiar with what it is, or the process architecture. At any rate, I don't think it's really the caches' fault, except that block usually has ~24 files open per profile (6x per for GPU, HTTP, media, app caches), if I did my math right. That's probably OK? @asanka: any idea how to route this?
,
Oct 26 2017
Not sure. +mojo folks: Comments / ideas on the process proliferation? The handle count doesn't seem all that excessive for the number of processes, but the process count itself might be a bit unexpected.
,
Jan 8
This should not be an issue anymore since there were no recent updates (or file handle leaks are captured in different tickets). |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by manoranj...@chromium.org
, Oct 19 2017