New issue
Advanced search Search tips

Issue 833403 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 9
Cc:
pnangunoori@chromium.org
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Browser crashes on startup

Reported by realart...@gmail.com, Apr 16 2018 
UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce the problem:
1. Open browser

What is the expected behavior?
The browser doesn't crash immediately

What went wrong?
The browser crashes half a second after launch. This has happened since i last updated (with apt, i installed it from Debian testing repo).

the file 'terminalcrash' is what shows when i open chromium through the terminal.

Using https://wiki.debian.org/Chromium/Debugging didn't work for me since i'm an idiot. Therefore i don't have that file.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes I updated last friday i think. I didn't have any issues before that.

Chrome version: 62.0.3202.89-1  Channel: n/a
OS Version: 4.15.0-2-amd64 (Debian testing buster)
Flash Version:
terminalcrash
1.3 KB View Download

Comment 1 by kkaluri@chromium.org, Apr 17 2018

Cc: kkaluri@chromium.org
Components: UI>Browser
Labels: Needs-Feedback
realarteeh@ Could you please help us with the below queries 
1. 16 digit crash id from chrome://crashes
2. Launch chrome browser with clean profile with no apps & extensions and let us know your observations
3. Launch chrome in incognito mode like "google-chrome-beta --incognito" and let us if the crash happens

Thank You...

Comment 2 by realart...@gmail.com, Apr 18 2018 

1. It says crash reporting is disabled / crash reporting is not available in Chromium.
2. Running the following from terminal: chromium --temp-profile
 worked. Everything there works as intended. It does show this in the terminal though:
[3986:3986:0418/020655.818734:ERROR:sandbox_linux.cc(346)] InitializeSandbox() called with multiple threads in process gpu-process.

3. Same issue as normal. It starts, and it shuts down immediately.
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 18 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

Comment 4 by pnangunoori@chromium.org, Apr 19 2018

Cc: pnangunoori@chromium.org
Labels: Needs-Feedback
realarteeh@ -- It looks like you are using very older version of Chrome. Please update your Chrome to latest #66.0.3359.106. If the issue still persists, please check the issue by reinstalling the chrome freshly in your system and let us know your observations if the issue still persists.

Thanks in advance!

Comment 5 by heg...@gmail.com, Apr 25 2018 

Hi, I have the same issue. It happened when running "google-chrome" to start the browser. Here is my system's information:

Linux <hostname> 4.1.12-112.14.15.el7uek.x86_64 #2 SMP Thu Feb 8 09:58:19 PST 2018 x86_64 x86_64 x86_64 GNU/Linux

The Chrome version I used is:
google-chrome-stable-66.0.3359.117-1.x86_64

Comment 6 by ligim...@chromium.org, Nov 9

Labels: Hotlist-DesktopUIChecked
Status: WontFix (was: Unconfirmed)
***Mass UI Triage***

We are unable to reproduce the bug. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue.

Chrome version : 72.0.3606.0, canary
►

Sign in to add a comment