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

Issue 596942 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Apr 2016
Cc:
█ ashej...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Chrome crashed overnight

Project Member Reported by cerickson@google.com, Mar 22 2016 
Chrome Version       : 50.0.2661.37
OS Version: Linux 3.13.0-74-generic

What steps will reproduce the problem?
1. Leave ~10 tabs across two profiles open overnight.

What is the expected result?
It's there in the morning.

What happens instead of that?
Sometimes it's gone.

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.37 Safari/537.36

Having seen this a bunch of times, I ran Chrome from a terminal this last time. Here are the last few dozen lines.

[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:fe80:0:0:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232145:WARNING:stunport.cc(379)] Jingle:Port[:0:0:stun:Net[em1:2620:0:1000:x:x:x:x:x/0:Unknown]]: StunPort: stun host lookup received error 0
[0318/232146:INFO:chromoting_client.cc(172)] Using direct connection for mux channel
[0318/232146:INFO:chromoting_client.cc(172)] Using direct connection for video channel
[5585:5585:0318/163245:ERROR:background_mode_manager_aura.cc(18)] Not implemented reached in virtual void BackgroundModeManager::DisplayClientInstalledNotification(const base::string16 &)
[0318/234034:ERROR:client_control_dispatcher.cc(44)] Cursor dimensions are out of bounds for SetCursor: 32655x0
[0318/182416:WARNING:proxy_config_service_linux.cc(550)] ~SettingGetterImplGSettings: leaking gsettings client
[1:1:0321/104633:ERROR:render_media_log.cc(21)] MediaEvent: PIPELINE_ERROR demuxer: could not open
[1:1:0321/104634:ERROR:render_media_log.cc(21)] MediaEvent: PIPELINE_ERROR demuxer: could not open
[1:1:0321/104634:ERROR:render_media_log.cc(21)] MediaEvent: PIPELINE_ERROR demuxer: could not open
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
Vector smash protection is enabled.
[5585:5585:0321/142235:ERROR:CONSOLE(1)] "Uncaught SyntaxError: Unexpected end of JSON input", source: chrome-extension://akimgimeeoiognljlfchpbkpfbmeapkh/index_compiled.html (1)
[5585:5585:0321/154309:ERROR:CONSOLE(0)] "Error in event handler for (unknown): SyntaxError: Unexpected token u in JSON at position 0
    at X (chrome-extension://noondiphcddnnabmjcihcjfbhfklnnep/content_script_compiled.js:24:161)
    at chrome-extension://noondiphcddnnabmjcihcjfbhfklnnep/content_script_compiled.js:24:131", source: https://www.google.com/_/chrome/newtab?espv=2&ie=UTF-8 (0)
ExceptionHandler::GenerateDump sys_pipe failed:Too many open files
ExceptionHandler::SendContinueSignalToChild sys_write failed:ExceptionHandler::WaitForContinueSignal sys_read failed:Bad file descriptor
Bad file descriptor
--2016-03-21 23:09:53--  https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 2607:f8b0:4005:800::200e, 216.58.192.14
Connecting to clients2.google.com (clients2.google.com)|2607:f8b0:4005:800::200e|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/3’

     0K
 Crash dump id:  6922a4f400000000 
                                                     1.37M=0s

2016-03-21 23:09:54 (1.37 MB/s) - ‘/dev/fd/3’ saved [16]

zsh: abort (core dumped)  google-chrome

Comment 1 by sekir...@gmail.com, Mar 24 2016 

I have the same problem, but it seems to be a bug of google-chrome, not chromium-browser's.

I can see /proc/sys/fs/file-nr is growing while google-chrome is running,

$ cat /proc/sys/fs/file-nr 
87552	0	809618
$ cat /proc/sys/fs/file-nr 
92000	0	809618

and when it reaches file-max (809618), the error "Too many open files" happens.

This means, google-chrome is leaking file descriptors. However, I couldn't reproduce this symptom with chromium-browser.

The version I tried are both 49.0.2623.87 Ubuntu 14.04 (64-bit).

Anyways, I think it's lucky if chrome crashes and leaked file descriptors would be released. If it goes worse, system crashes and I'd lost a lot of running tasks and unsaved changes today...

/var/log/syslog:
Mar 24 13:05:32 kernel: [183074.531689] VFS: file-max limit 809618 reached
Mar 24 13:05:32 kernel: [183074.617843] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (28672, 6, 8192, -23)
Mar 24 13:05:32 kernel: [183074.665339] compiz[2679]: segfault at 10 ip 00007f4311103b5c sp 00007ffd13880690 error 4 in r600_dri.so[7f4310e4d000+399000]
Mar 24 13:05:39 kernel: [183082.064785] VFS: file-max limit 809618 reached
Mar 24 13:05:41 gnome-session[2496]: WARNING: Child process 2679 was already dead.
Mar 24 13:05:42 gnome-session[2496]: WARNING: Application 'compiz.desktop' killed by signal 11
Mar 24 13:05:42 gnome-session[2496]: WARNING: App 'compiz.desktop' respawning too quickly
Mar 24 13:05:42 gnome-session[2496]: WARNING: Could not get session class: Too many open files
Mar 24 13:05:42 gnome-session[2496]: dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Too many open files.  dconf will not work properly.
Mar 24 13:05:42 gnome-session[2496]: CRITICAL: We failed, but the fail whale is dead. Sorry....

Comment 2 by ashej...@chromium.org, Apr 1 2016

Cc: ashej...@chromium.org
Labels: Needs-Feedback Hotlist-Google
Thanks for the report. Are you still facing the above issue on latest chrome 50.0.2661.57 ?

Stack trace for internal use:
-----------------------------
go/crash/6922a4f400000000

Appreciate your help.

Thank you!

Comment 3 by cerickson@google.com, Apr 8 2016 

It happened once more on my workstation, and once more on my laptop, since comment #2, but in both cases my computer had only recently installed that latest version, so it was almost certainly the previous version that crashed. I don't think I have seen another overnight crash since then. I did have Chrome crash once while I was using it, but I didn't run it from a terminal that time, couldn't find any messages to definitely link to it, and didn't see any new crashes in chrome:crashes.

So am I still facing it? Maybe.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 9 2016

Labels: -Needs-Feedback Needs-Review
Owner: ashej...@chromium.org
Thank you for providing more feedback. Adding requester "ashejole@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ashej...@chromium.org, Apr 25 2016

Labels: -Needs-Review
Owner: ----
Status: WontFix (was: Unconfirmed)
No, I guess. But, if you come across this crash again do file a new bug.
I am closing this for now as I am unable to reproduce the above issue on 50.0.2661.87.


Thank you!
►

Sign in to add a comment