New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 593914 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
█ ranjitkan@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Memory leak possibly causing OSX to freeze and reboot

Reported by a...@polkaroo.net, Mar 10 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Firefox/45.0

Steps to reproduce the problem:
1. Chrome running on late-2015 retina iMac OSX 10.11.3
2. Wait

What is the expected behavior?

What went wrong?
Whole mac freezes, then reboots. Apple says it is related to Chrome and Goodle Drive.

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 49.0.2623.87  Channel: stable
OS Version: OS X 10.11.3
Flash Version: 

iMac (Retina 5K, 27-inch, Late 2015)
4 GHz Intel Core i7
16 GB 1867 MHz DDR3
AMD Radeon R9 M395X 4096 MB
apple_imac_crash_email.txt
3.8 KB View Download

Comment 1 by a...@polkaroo.net, Mar 10 2016 

Note that the screen freezes for 20-30 seconds (mouse cursor won't move) before going black. Then it reboots. There is no kernel panic screen and the system does not offer to send a report after coming back up (like I would expect.)

Chrome should not be able to cause this without an Apple bug allowing it to. It looks like Chrome has has triggered a bug like this before. http://www.cnet.com/news/google-yes-chrome-is-crashing-macbooks/

Comment 2 by ranjitkan@chromium.org, Mar 11 2016

Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on chrome stable version 49.0.2623.87 on MAC 10.11.3 Retina Pro. Request you to please try a system reboot and disable al the third party extensions and please update us with your observations.

Also do you need to kill the chrome process, if yes a crash ID would be generated in chrome://crashes. Can you please help us with the crash ID generated.

Thanks.!

Comment 3 by rsesek@chromium.org, Mar 14 2016 

The leak you're reporting is  bug 428858  and is generally benign. It wouldn't cause the system to freeze.
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 14 2016

Labels: -Needs-Feedback Needs-Review
Owner: ranjitkan@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "ranjitkan@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ranjitkan@chromium.org, Mar 22 2016

Labels: -Needs-Review Needs-Feedback
Owner: ----
Status: Unconfirmed (was: Assigned)

Comment 6 by a...@polkaroo.net, Mar 22 2016 

Thanks Ranjit. I did not have to kill Chrome. The whole video system would just freeze for 20-30 seconds (no mouse movement, no beachball) and then it would reboot. No kernel panic logs, etc.

I tried removing Chrome and still had the rebooting problem. It was only after removing the Google Software Update that came with Chrome that the system stabilized. I later reinstalled the OS and Chrome from scratch and have not seen the problem again yet. So I'm baffled.
Project Member

Comment 7 by sheriffbot@chromium.org, Mar 23 2016

Labels: -Needs-Feedback Needs-Review
Owner: ranjitkan@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "ranjitkan@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by ranjitkan@chromium.org, Mar 28 2016

Owner: ----
Status: WontFix (was: Assigned)
@ amos: Thanks for the update. Closing the issue for now. Please feel free to reopen or raise a new issue if it reappears 

Thanks.!
►

Sign in to add a comment