Chrome can't be closed after opening the developer tools
Reported by
tho...@novemberfive.co,
Nov 11 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome 2. Open the developer tools on any webpage 3. Close Chrome What is the expected behavior? Chrome closes What went wrong? Chrome doesn't close. Instead, it hangs and I need to force close it. Did this work before? N/A Chrome version: 62.0.3202.89 Channel: stable OS Version: OS X 10.13.1 Flash Version: This is the case already for a long time (at least a year). After opening the developer tools, I also see that Chrome starts using a lot more CPU than usual. In Chrome Canary I never had this issue, but after updating Chrome stable, the issue persists
,
Nov 12 2017
Here you go
,
Nov 12 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
,
Nov 12 2017
Thank you for the feeadback and the attached trace.
,
Nov 13 2017
"Unable to reproduce the issue on the reported chrome version stable 62.0.3202.89 and on the latest stable 62.0.3202.94 using Mac 10.12.6, windows 10 and Ubuntu 14.04. Attaching the screen cast of the same. @Reporter: Could you please check the screen cast and let us know if we have missed any steps in reproducing the issue. Thanks!"
,
Nov 13 2017
Thread 1 is waiting for other work before shutting down:
1971 Thread_11960439 DispatchQueue_1: com.apple.main-thread (serial)
+ 1971 start (in libdyld.dylib) + 1 [0x7fff512d9145]
+ 1971 main (in Google Chrome) + 404 [chrome_exe_main_mac.cc:169]
+ 1971 ChromeMain (in Google Chrome Framework) + 175 [chrome_main.cc:0]
+ 1971 content::ContentMain(content::ContentMainParams const&) (in Google Chrome Framework) load address 0x10b42a000 + 0x1745084 [content_main.cc:19]
+ 1971 service_manager::Main(service_manager::MainParams const&) (in Google Chrome Framework) load address 0x10b42a000 + 0x30163b0 [main.cc:469]
+ 1971 content::ContentMainRunnerImpl::Run() (in Google Chrome Framework) load address 0x10b42a000 + 0x1745ace [content_main_runner.cc:709]
+ 1971 content::BrowserMain(content::MainFunctionParams const&) (in Google Chrome Framework) load address 0x10b42a000 + 0x659f28 [memory:2233]
+ 1971 content::BrowserMainRunnerImpl::Shutdown() (in Google Chrome Framework) load address 0x10b42a000 + 0x66077c [browser_main_runner.cc:214]
+ 1971 content::BrowserMainLoop::ShutdownThreadsAndCleanUp() (in Google Chrome Framework) load address 0x10b42a000 + 0x65eb8a [trace_event.h:1072]
+ 1971 base::internal::TaskTracker::Shutdown() (in Google Chrome Framework) load address 0x10b42a000 + 0x1befd6f [task_tracker.cc:212]
+ 1971 base::internal::TaskTracker::PerformShutdown() (in Google Chrome Framework) load address 0x10b42a000 + 0x1befe14 [lock.h:26]
+ 1971 base::WaitableEvent::Wait() (in Google Chrome Framework) load address 0x10b42a000 + 0x1be400f [waitable_event_mac.cc:106]
+ 1971 base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) (in Google Chrome Framework) load address 0x10b42a000 + 0x1be40d5 [waitable_event_mac.cc:147]
+ 1971 mach_msg (in libsystem_kernel.dylib) + 60 [0x7fff5141f390]
+ 1971 mach_msg_trap (in libsystem_kernel.dylib) + 10 [0x7fff5141fe76]
And it looks like it's waiting on a file in devtools:
1971 Thread_12505948: TaskSchedulerBackgroundBlockingWorker
+ 1971 thread_start (in libsystem_pthread.dylib) + 13 [0x7fff51562c5d]
+ 1971 _pthread_start (in libsystem_pthread.dylib) + 377 [0x7fff5156356d]
+ 1971 _pthread_body (in libsystem_pthread.dylib) + 340 [0x7fff515636c1]
+ 1971 base::(anonymous namespace)::ThreadFunc(void*) (in Google Chrome Framework) load address 0x10b42a000 + 0x1bfb957 [platform_thread_posix.cc:77]
+ 1971 base::internal::SchedulerWorker::Thread::ThreadMain() (in Google Chrome Framework) load address 0x10b42a000 + 0x1bebb18 [scheduler_worker.cc:73]
+ 1971 base::internal::TaskTracker::RunNextTask(base::internal::Sequence*) (in Google Chrome Framework) load address 0x10b42a000 + 0x1bf0135 [memory:2543]
+ 1971 base::internal::TaskTrackerPosix::PerformRunTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*) (in Google Chrome Framework) load address 0x10b42a000 + 0x1bf0a13 [memory:2543]
+ 1971 base::internal::TaskTracker::PerformRunTask(std::__1::unique_ptr<base::internal::Task, std::__1::default_delete<base::internal::Task> >, base::internal::Sequence*) (in Google Chrome Framework) load address 0x10b42a000 + 0x1bf04bb [task_tracker.cc:335]
+ 1971 base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) (in Google Chrome Framework) load address 0x10b42a000 + 0x1b85424 [callback_forward.h:11]
+ 1971 base::internal::Invoker<base::internal::BindState<void (DevToolsFileWatcher::*)(base::FilePath), base::internal::UnretainedWrapper<DevToolsFileWatcher>, base::FilePath>, void ()>::RunOnce(base::internal::BindStateBase*) (in Google Chrome Framework) load address 0x10b42a000 + 0x3e2b906 [bind_internal.h:194]
+ 1971 DevToolsFileWatcher::SharedFileWatcher::AddWatch(base::FilePath const&) (in Google Chrome Framework) load address 0x10b42a000 + 0x3e29fc3 [devtools_file_watcher.cc:99]
+ 1945 DevToolsFileWatcher::SharedFileWatcher::GetModificationTimes(base::FilePath const&, std::__1::map<base::FilePath, base::Time, std::__1::less<base::FilePath>, std::__1::allocator<std::__1::pair<base::FilePath const, base::Time> > >*) (in Google Chrome Framework) load address 0x10b42a000 + 0x3e2a2c8 [devtools_file_watcher.cc:109]
+ ! 1625 base::FileEnumerator::Next() (in Google Chrome Framework) load address 0x10b42a000 + 0x1b8a4fc [file_enumerator_posix.cc:24]
+ ! : 1625 stat$INODE64 (in libsystem_kernel.dylib) + 10 [0x7fff5142a982]
,
Nov 13 2017
cc'ing dgozman@ OP@, do you have Workspaces setup in DevTools?
,
Nov 15 2017
,
Dec 18 2017
,
Dec 12
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by meh...@chromium.org
, Nov 12 2017