New issue
Advanced search Search tips

Issue 848875 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome quits repeatedly (Linux, mesa, Solus/Gentoo)

Reported by cristian...@gmail.com, Jun 1 2018

Issue description

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

Steps to reproduce the problem:
Usually caused by browsing content heavy websites like huobi.pro or web.whatsapp.com. 

What is the expected behavior?

What went wrong?
Initially, just individual tabs will crash. Whole browser segfaults after some time.

Crashed report ID: Failed to get crash dump id.

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 68.0.3438.3  Channel: n/a
OS Version: 68.0.3438.3
Flash Version: 24.0.0.189

Whenever it crashes, I get:
[1988:1988:0527/094733.861007:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
[1:15:0527/094735.807687:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
Cannot exec gzip.
sys_waitpid() for gzip process failed.

Unexpected crash report id length
Failed to get crash dump id.
Report Id: 
Cannot exec gzip.
sys_waitpid() for gzip process failed.

Unexpected crash report id length
Failed to get crash dump id.
Report Id: 
Cannot exec gzip.
sys_waitpid() for gzip process failed.

Unexpected crash report id length
Failed to get crash dump id.
Report Id: 

Solus/Gentoo (tested on both), 280x, mesa-18.1.
 
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
cristiano04@ Could you please help us with 16 digit crash id from chrome://crahses for further triage.


Crash.png
37.4 KB View Download
@kkaluri the crash is not reported at all, as is reported by the string 'Failed to get crash dump id':

Crashes (0)
You have no recently reported crashes. Crashes that occurred when crash reporting was disabled will not appear here. 

It's worth noting I tried with the gpu disabled flag too, but the crash still occurred. 
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 6 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: rbasuvula@chromium.org
Components: Internals>GPU
Labels: Needs-Triage-M68 Needs-Feedback
Tested in chrome # 67.0.3396.87 and Canary #69.0.3464.0 on Linux debian rodete and not able to reproduce the issue.Please find the screen shots for your reference.

@ cristiano04: Could you please let me know if i have missed anything and if possible,Please create new profile without extensions and apps.Re-check once let us know the observations of the issue which would help us to triage the issue further.

Thanks in Advance.
848875.png
271 KB View Download
Experiencing similar failure (Lost UI Context) but without the need to browse heavy pages. My launch page is a "public wifi landing page." 

cary@lemur:~$ google-chrome --app=chrome://crashes
[3960:3960:0623/052022.529257:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
[1:9:0623/052022.629660:ERROR:command_buffer_proxy_impl.cc(133)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
Trace/breakpoint trap (core dumped)
cary@lemur:~$ google-chrome --version
Google Chrome 67.0.3396.87 
cary@lemur:~$ uname -a
Linux lemur 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Follow-up: Installed Chromium as a snap. 

cary@lemur:~$ chromium --version
Chromium 67.0.3396.62

Multiple start-up attempts PASSED.

Even after logging in and loading all five extensions, Chromium still works.


Sign in to add a comment