New issue
Advanced search Search tips

Issue 868887 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Jul 30
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Browser completely crashes and reloads

Reported by david.st...@gmail.com, Jul 30

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS aarch64 10920.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3505.0 Safari/537.36
Platform: 10920.0.0 (Official Build) canary-channel elm

Steps to reproduce the problem:
1. Normal use and everything freezes
2. Browser reloads
3. 

What is the expected behavior?
No crashes

What went wrong?
Browser crashes

Crashed report ID: b439292f24137f82

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes July 28

Chrome version: 70.0.3505.0  Channel: canary
OS Version: 10920.0.0
Flash Version: 30.0.0.142

I have had 2 crashes this morning. A second crash report  Crash Report ID 356b1f4f37c5e7c6
 
Mergedinto: 863318
Status: Duplicate (was: Unconfirmed)
Link to 863318 doesn't seem to exist or is this some internal report?
Can you confirm what tabs are open when this happens? The bug appears to be related to WebUI, so is mostly likely caused by a tab open to a chrome:// URL (ie, chrome://settings, or chrome://flags, etc).

I've been trying to reproduce (unsuccessfully) and this may help to track down what's going on.

(yes, the linked bug is a "Google internal report", but it is definitely related to the same issue)
I may have had chrome://crashes and chrome://version opened. I also think I had several Secure Shell tabs open (3 to 5). This morning I likely didn't have more than 25 tabs open of which a dozen are pinned.  I believe I crashed twice yesterday and twice this morning. Since this morning I haven't crashed again although I have updated since the last crash. 

I have the chrome:// URI open and I will watch for further issues and update. Let me know if there is anything else I can do to help.

Here are the crash reports from yesterday although I am not sure which might be related to the browser crash.

Uploaded Crash Report ID 8fdc19745d5952c3 (Local Crash ID: Chrome)
Crash report uploaded on Sunday, July 29, 2018 at 5:59:24 PM

Provide additional details

Uploaded Crash Report ID 3009ebd5748e08ad (Local Crash ID: Chrome)
Crash report uploaded on Sunday, July 29, 2018 at 5:58:55 PM

Provide additional details

Uploaded Crash Report ID 975cdae7c76bc753 (Local Crash ID: Chrome)
Crash report uploaded on Sunday, July 29, 2018 at 5:54:38 PM

Provide additional details

Uploaded Crash Report ID ff51e01db5cb3780 (Local Crash ID: Chrome)
Crash report uploaded on Sunday, July 29, 2018 at 3:16:42 PM

Provide additional details

Uploaded Crash Report ID eb097c073c6afad7 (Local Crash ID: Chrome)
Crash report uploaded on Sunday, July 29, 2018 at 2:02:09 PM

Provide additional details

Uploaded Crash Report ID 1bfd2ed1147cebf3 (Local Crash ID: ChromeOS)
Crash report uploaded on Sunday, July 29, 2018 at 1:54:36 PM

Provide additional details
Owner: chrisha@chromium.org
Okay, looking at your crash reports about half of them are clearly related to the same issue in 863318. This should be fixed in tomorrow's canary. If you're able to confirm whether the problem goes away after a day or two that would be great.
Glad there was some evidence. I will report back. 

Many thanks,
Another full crash this afternoon, although I don't see the crash report from that crash. Between the afternoon of July 31 and now I have accumulated 50 crash reports. 
Yeah, the fix took a little longer to land than anticipated. Landed last night, so will finally be in tomorrow (Friday's) canary. Sorry for the hassle.
Just hope I am being helpful. Another crash this morning and again no crash report on the list. 
Several more crashes. These are lid closed crashes and the Browser does not reload. 
Uploaded Crash Report ID 05c212182ddcbaa3 (Local Crash ID: ChromeOS)
Crash report uploaded on Friday, August 3, 2018 at 5:12:10 PM

Provide additional details

Uploaded Crash Report ID 5fd7478c55b60ea1 (Local Crash ID: ChromeOS)
Crash report uploaded on Friday, August 3, 2018 at 5:09:50 PM

Provide additional details

Uploaded Crash Report ID e2659f0f5df48872 (Local Crash ID: ChromeOS)
Crash report uploaded on Friday, August 3, 2018 at 5:01:44 PM

Provide additional details 
Your first crash reports were related to issue #863318 that I fixed last week. Since that fix went through I've seen 0 related crashes.

The crashes you are continuing to see are due to another unrelated bug from what I can see. That bug is being tracked in issue #865442.
Sadly I am unable to update to the version you fixed due to  issue #870816 
That bug hasn't been looked at as far as I know or acknowledged. 
In spite of an available update today, I am still unable to update. Via the update engine logs it shows a firmware update failure.
update_engine.log
288 KB View Download
I have been unable to test this for the past 3 weeks as I could not return to Canary. So far, I have not experienced any crashes.
I have had one complete crash today, but there is no crash report. 
Two complete browser crashes this morning. I don't see a crash report for either of them. 
Third complete crash today with NO crash report.

Sign in to add a comment