Issue metadata
Sign in to add a comment
|
Chome 62 crashes entire mac
Reported by
joey2...@gmail.com,
Oct 27 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:56.0) Gecko/20100101 Firefox/56.0 Steps to reproduce the problem: 1. Start Chrome 2. 3. What is the expected behavior? Chrome works What went wrong? The entire macbook locks up / crashes. Crashed report ID: no How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes V61 Chrome version: V62 Channel: stable OS Version: OS X 10.13 Flash Version: Shockwave Flash 27.0 r0 I updated to v62 yesterday. I didnt have any problems updating or restarting while plugged into my dock. When i went home my Mac crashed on opening. I restarted multiple times and it always would crash restoring programs. I logged into guest and it worked and didnt lock up. I started chrome and it locked up. I uninstalled chrome, then logged into my normal user. It loaded and worked. I redownloaded chrome v62 and copied it to applications. As soon as I started it, it locked the whole macbook up. I restarted, logged in as guest, deleted chrome. Everything is working fine now. But I cant provide much more info as when I try to run chrome, it literally locks the whole system up.
,
Oct 27 2017
I don't think that is possible. As I said it literally locks the entire MacBook up. I can only use the system again after a restart, after which chrome would no longer be in the activity monitor. Right?
,
Oct 27 2017
You say it crashes the whole Browser. Any chance to send us the Apple Crash log? Thanks in advance.
,
Oct 27 2017
That was the only option in the dropdown, it crashes the whole MacOS. So I have a crashreport here from last night and today when I tested again. It still crashes. I also have included video of what I am doing and showing the crash. This has to have something to do with my docking of the laptop. When I use the internal display chrome crashes the whole laptop. When I use the dock and the external displays chrome actually loads fine.
,
Oct 27 2017
Here is the video of it working on my external monitors
,
Oct 27 2017
Thank you for providing more feedback. Adding requester "mehmet@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 27 2017
Looks like those system crash logs have something to do with CloudKit which should be unrelated to Chrome. Unfortunately, neither of the videos work for me.
I'm assuming you can't load Chrome long enough to upload a crash from chrome://crashes? If you can, please paste the Crash ID. It would look something like
Uploaded Crash Report ID {THIS IS WHAT WE NEED} (Local Crash ID: {IGNORE THIS}
,
Oct 27 2017
,
Oct 27 2017
,
Oct 27 2017
The videos were H265 to keep them under the 10MB limit, probably cant play. Here are links to the original ones on dropbox. https://www.dropbox.com/s/uzh727r8cmwl2t1/IMG_1197.MOV?dl=0 https://www.dropbox.com/s/5n8rojzhhp1sqos/IMG_1198.MOV?dl=0 I cannot get chrome to load at all. I click the application icon, 1 second later the hole laptop freezes.
,
Oct 27 2017
Thank you for providing more feedback. Adding requester "lgrey@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 27 2017
I take that back, I can get it to load when connected to my external monitors. Doing that I was able to get: Local Crash ID b20ea8d3-8c44-4ffa-94fc-6d92409ee415 Crash report captured on Thursday, October 26, 2017 at 10:11:59 PM (upload requested by user, not yet uploaded)
,
Oct 27 2017
If you can get back in, can you check back in a bit and see if it uploaded? The server crash ID is what we need (won't appear until the upload is complete)
,
Oct 27 2017
This doesn't list the crash today (about 12:33p EST) though that happened when I recorded that video I liked above. So im not sure if these crash reports are for the actual crash that happens. Though last night's might.
,
Oct 27 2017
My crash comment keeps getting deleted. Uploaded Crash Report ID 410b4b02decc0ef7 (Local Crash ID: b20ea8d3-8c44-4ffa-94fc-6d92409ee415) Crash report captured on Thursday, October 26, 2017 at 10:11:59 PM, uploaded on Friday, October 27, 2017 at 1:59:38 PM
,
Oct 27 2017
That report looks like a purposeful termination due to system hang. +ccameron@ who might have some insight since it seems like it works with different display hardware.
,
Oct 31 2017
ccameron@ - Could you please have a look into the issue as per comment #18. Thanks...!!
,
Nov 1 2017
[Mac triage] I crunched the videos down a bit. Thing that might be worth trying in the mean time, in order of effort:
1. 10.13.1 is out, try updating?
2. Run Chrome from a Terminal with the --user-data-dir= flag to see if it helps. For example:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=Desktop/tmp_user_data_dir
3. If you *really* want to help out, you could try creating a sysdiagnose. Hold command+option+control+shift and type '.'. Then, wait ~2 minutes before you reboot. Hopefully, there will be a zip file in /tmp. You can unzip this and browse through the system logs in Console (it'll be the largest file at the top level of the zip), and share any relevant lines. If that fails, you can also try to run sysdiagnose after rebooting (/tmp will open in the Finder when it's done).
,
Nov 2 2017
I would guess this to be to NVIDIA driver instability in 10.13.
,
Nov 2 2017
Interesting... we haven't seen this behavior before. It's even weirder that this works *on* external monitors, which force the discrete GPU. So far, we've only seen issues when the external monitor is connected. This makes me suspect an Intel issue, not an NVidia one. I'm really surprised we haven't seen this... I think we have similar hardware that we're testing on. joey2250@, to make sure I understand correctly, Chrome 61 worked correctly on your mac with the 10.13.1 update (you tried 61 without an external monitor and it worked), but after updating to 62, things started breaking? Also, we had some workarounds and fixes land in the latest build of Chrome 62 - the one on the crash report you link has now been updated further. Can you make sure you have Chrome version 62.0.3202.62 (maybe via the external monitor?) and see if that addresses any of your problems? Thanks!
,
Nov 2 2017
joey2250@ can you please provide the contents of the page: about:gpu Plaintext copy/paste is fine. You can feel free to leave off the logging at the bottom.
,
Nov 3 2017
I think you may be right, and this is an Intel integrated GPU issue. Starting today the issue has gotten worse. It has moved beyond chrome, I cannot boot my laptop while using the integrated display. It will, however, boot when connected to the external monitors. During the black screen & progress bar, it gets about 3/4 through and stops. I was able to force the internet recovery boot, and even that wouldn't load all of the time. I was able to boot into single user and viewing the verbosity boot log, I can see it stopping, but it's not always at the same log message. It even wouldnt boot using the HighSierra install USB. That is, of course, unless the externals were connected lol. I even reformatted then reinstalled 10.13, and it still would not boot unless connected to the externals. This is very odd, but I think its safe to say its probably not a chrome issue now. But to answer your questions from above: Chrome v61 and 10.13 worked, v62 and 10.13 crashed unless connected to the external monitor. I had recently installed 10.13.1 and it worked connected to the external monitors, but I hadn't tested on the integrated display yet.
,
Nov 4 2017
[mac triage] moving out of triage. joey2250@ thanks for filing the report! If you are able, the contents of about:gpu may still help us track this issue in case it spreads to other users.
,
Nov 6 2017
No problem, sorry to have wasted your time. It originally really looked like it was a chrome issue :) Attached are the contents of my about:gpu page.
,
Nov 6 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lgrey@chromium.org
, Oct 27 2017