New issue
Advanced search Search tips

Issue 793805 link

Starred by 2 users
Status: Duplicate
Merged: issue 781825
Owner: ----
Closed: Dec 2017
Cc:
sorin@chromium.org
rsesek@chromium.org
meh...@chromium.org
waff...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome won't quit in high sierra on macbook pro

Reported by joe....@gmail.com, Dec 11 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36

Steps to reproduce the problem:
1. install high sierra
2.Open Chrome
3.Try to quit Chrome 

What is the expected behavior?
Chrome should close

What went wrong?
It won't quit and if you try to force quit it, you won't be able to open it again. Then you have to restart the macbook pro.

Did this work before? Yes Sierra

Chrome version: 63.0.3239.84  Channel: stable
OS Version: OS X 10.13.1
Flash Version: 

I think there are also related issues with that: for example, chrome now consumes a lot of power (200 energy points in Activity Monitor). Also the laptop can't be sleep, wake up or shutdown properly because  Chrome refuses to quit.

Comment 1 by meh...@chromium.org, Dec 11 2017

Labels: Needs-Feedback
Can you please grab the sample of the hanging Chrome process in the Activity.app and attach it here? Thanks.

Comment 2 by joe....@gmail.com, Dec 11 2017 

Here you go. Thanks. --Joe
Sample of Google Chrome.txt
104 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 11 2017

Cc: meh...@chromium.org
Labels: -Needs-Feedback
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

Comment 4 by meh...@chromium.org, Dec 11 2017

Cc: rsesek@chromium.org
Labels: Stability-Hang
Great, that you for your feedback and the attached Sample.

Comment 5 by rsesek@chromium.org, Dec 11 2017

Cc: sorin@chromium.org waff...@chromium.org
This looks similar to  issue 781825  where the main thread is waiting to shut down because of base::DeleteFile from the component updater.

    280 Thread_9210   DispatchQueue_1: com.apple.main-thread  (serial)
    + 280 start  (in libdyld.dylib) + 1  [0x7fff624ad145]
    +   280 main  (in Google Chrome) + 404  [chrome_exe_main_mac.cc:169]
    +     280 ChromeMain  (in Google Chrome Framework) + 175  [chrome_main.cc:0]
    +       280 content::ContentMain(content::ContentMainParams const&)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x185e934  [content_main.cc:19]
    +         280 service_manager::Main(service_manager::MainParams const&)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x305adca  [main.cc:469]
    +           280 content::ContentMainRunnerImpl::Run()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x185f38a  [content_main_runner.cc:710]
    +             280 content::BrowserMain(content::MainFunctionParams const&)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x727d58  [memory:2233]
    +               280 content::BrowserMainRunnerImpl::Shutdown()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x72dfbc  [browser_main_runner.cc:202]
    +                 280 content::BrowserMainLoop::ShutdownThreadsAndCleanUp()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x72c0a3  [trace_event.h:1088]
    +                   280 base::internal::TaskTracker::Shutdown()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca376f  [task_tracker.cc:243]
    +                     280 base::internal::TaskTracker::PerformShutdown()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca3814  [lock.h:26]
    +                       280 base::WaitableEvent::Wait()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c971df  [waitable_event_mac.cc:107]
    +                         280 base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c972b5  [waitable_event_mac.cc:149]
    +                           280 mach_msg  (in libsystem_kernel.dylib) + 60  [0x7fff625f3390]
    +                             280 mach_msg_trap  (in libsystem_kernel.dylib) + 10  [0x7fff625f3e76]

    280 Thread_9302: TaskSchedulerBackgroundBlockingWorker
    + 280 thread_start  (in libsystem_pthread.dylib) + 13  [0x7fff62736c5d]
    +   280 _pthread_start  (in libsystem_pthread.dylib) + 377  [0x7fff6273756d]
    +     280 _pthread_body  (in libsystem_pthread.dylib) + 340  [0x7fff627376c1]
    +       280 base::(anonymous namespace)::ThreadFunc(void*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1cafe17  [platform_thread_posix.cc:77]
    +         280 base::internal::SchedulerWorker::Thread::ThreadMain()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c9eb50  [ref_counted.h:574]
    +           280 base::internal::TaskTracker::RunNextTask(scoped_refptr<base::internal::Sequence>, base::internal::CanScheduleSequenceObserver*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca3ca7  [memory:2543]
    +             280 base::internal::TaskTrackerPosix::RunOrSkipTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*, bool)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca4ebc  [memory:2543]
    +               280 base::internal::TaskTracker::RunOrSkipTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*, bool)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca434c  [task_tracker.cc:411]
    +                 280 base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c3a62c  [callback_forward.h:11]
    +                   280 base::(anonymous namespace)::PostTaskAndReplyRelay::RunTaskAndPostReply()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1caffd9  [callback_forward.h:11]
    +                     280 component_updater::ComponentInstaller::StartRegistration(scoped_refptr<component_updater::ComponentInstaller::RegistrationInfo> const&, component_updater::ComponentUpdateService*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x313588d  [iterator:1359]
    +                       280 base::DeleteFile(base::FilePath const&, bool)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c48383  [file_util_posix.cc:274]
    +                         280 unlink  (in libsystem_kernel.dylib) + 11  [0x7fff625fa2e0]
    +                           280 __unlink  (in libsystem_kernel.dylib) + 10  [0x7fff625fd5f2]
    280 Thread_9303: TaskSchedulerBackgroundBlockingWorker
    + 280 thread_start  (in libsystem_pthread.dylib) + 13  [0x7fff62736c5d]
    +   280 _pthread_start  (in libsystem_pthread.dylib) + 377  [0x7fff6273756d]
    +     280 _pthread_body  (in libsystem_pthread.dylib) + 340  [0x7fff627376c1]
    +       280 base::(anonymous namespace)::ThreadFunc(void*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1cafe17  [platform_thread_posix.cc:77]
    +         280 base::internal::SchedulerWorker::Thread::ThreadMain()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c9eb50  [ref_counted.h:574]
    +           280 base::internal::TaskTracker::RunNextTask(scoped_refptr<base::internal::Sequence>, base::internal::CanScheduleSequenceObserver*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca3ca7  [memory:2543]
    +             280 base::internal::TaskTrackerPosix::RunOrSkipTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*, bool)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca4ebc  [memory:2543]
    +               280 base::internal::TaskTracker::RunOrSkipTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*, bool)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1ca434c  [task_tracker.cc:411]
    +                 280 base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c3a62c  [callback_forward.h:11]
    +                   280 base::(anonymous namespace)::PostTaskAndReplyRelay::RunTaskAndPostReply()  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1caffd9  [callback_forward.h:11]
    +                     280 component_updater::ComponentInstaller::StartRegistration(scoped_refptr<component_updater::ComponentInstaller::RegistrationInfo> const&, component_updater::ComponentUpdateService*)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x313588d  [iterator:1359]
    +                       280 base::DeleteFile(base::FilePath const&, bool)  (in Google Chrome Framework)  load address 0x106eb3000 + 0x1c48383  [file_util_posix.cc:274]
    +                         280 unlink  (in libsystem_kernel.dylib) + 11  [0x7fff625fa2e0]
    +                           280 __unlink  (in libsystem_kernel.dylib) + 10  [0x7fff625fd5f2]

Comment 6 by rsesek@chromium.org, Dec 11 2017 

Both issues were reported on 10.13 so I wonder if this is APFS related.

Comment 7 by sorin@chromium.org, Dec 11 2017

Components: Internals>Installer>Components
Mergedinto: 781825
Status: Duplicate (was: Unconfirmed)
I don't have to expertise to look into macOS system related issues. This is most likely not related to the component updater implementation.
►

Sign in to add a comment