New issue
Advanced search Search tips

Issue 676833 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 676960
Owner: ----
Closed: Dec 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chromium dies, constantly and every time, on a segmentation fault after about 6 minutes on OS X 10.11.6

Reported by laine.j....@gmail.com, Dec 23 2016

Issue description

Chrome Version       : 57.0.2961.0 (64-bit)
URLs (if applicable) : Any URL or even just the NTP will do.
Other browsers tested: No other browsers tested because, well, read on.

> What steps will reproduce the problem?

(1) Launch Chromium on OS X 10.11.6 (El Capitan) and let it either idle or load any URL.
(2) Wait less than 10 minutes.
(3) Chromium crashes.

> What is the expected result?

Chromium process keeps running for longer than 6 minutes. Preferably hours like it does on other releases of OS X.

> What happens instead?

Chromium crashes after about 6 minutes, every time, regardless of URL.

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

The exact same version of Chromium works just fine on an identical Macbook Pro running OS X 10.9.5 (Mavericks); so, it seems that this is only connected with Chromium running on OS X 10.11.6 (El Capitan). The System Integrity Protection feature is enabled on the 10.11.6, and this might have something to do with the crash, albeit I'm rather hard pressed to see how exactly the two might be connected.

 
chromium.crash.report.0.txt
85.6 KB View Download
de634404-864e-404a-9af1-3183c6815423.dmp
486 KB Download
chromium.crash.report.1.txt
85.5 KB View Download
6161f9f1-5570-46fa-8f6c-452a97bae849.dmp
477 KB Download

Comment 1 by arikrak@google.com, Dec 26 2016

I ran into the same issue. I'm attaching the end of the chrome debug log.
end_of_chrome_debug.log
1.7 KB View Download

Comment 2 by arikrak@google.com, Dec 26 2016

I just upgraded my Mac to OS to version 10.12.2 (from 10.11) but I'm still encountering the same issue on Chrome Version 57.0.2963.0 canary (64-bit). 
Mergedinto: 676960
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment