Opening a .cpuprofile hangs Chrome Dev Tools and occasionally crashes Chrome fully
Reported by
b...@toplayfor.co.uk,
Jan 15 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Open up Dev Tools -> Profiles 2. Click Load -> Load the attached file in this issue 3. It will appear in the profiles on the left, but Dev Tools will hang when selecting it, or, on occasion, crash the browser. 1 time out of 10, it'll load properly. What is the expected behavior? You can see the .cpuprofile graph when selecting it. What went wrong? Dev Tools crashes/hangs as above. Also note: my Macbook's fan goes into overdrive when this occurs. Did this work before? N/A Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.12.1 Flash Version: Shockwave Flash 24.0 r0
,
Jan 16 2017
I've attached the OSX crash file. I've also attached a screenshot of Activity Monitor showing that as soon as I click on the profile, Chrome starts using 100% CPU time. Also - I have Profiles set by default to the graph view rather than the tree view, if that makes a difference. This is reproducible on a fresh opening of Chrome with no tabs (not sure if relevant, but thought will add anyway).
,
Jan 17 2017
Do you have a crash id from chrome://crashes ?
,
Jan 18 2017
Sorry - didn't know this was a thing. I've clicked the "send now" button for the error report but am getting "(upload requested by user, not yet uploaded)". Don't know how long this takes, been saying it for a while. Anyway, the ID is: 77180341-322d-4cb4-8d5e-3c220f447ad9
,
Jan 20 2017
Just confirming that the crash report with the above ID has been sent.
,
Jan 20 2017
Do you have the server id?
,
Jan 20 2017
5041ed6580000000
,
Jan 20 2017
Seems to be not caused by CPU profile. ProfileDestroyer is an unrelated entity. 0x000000010e57c052 (Google Chrome Framework -profile_destroyer.cc:130 ) ProfileDestroyer::~ProfileDestroyer() 0x000000010e57c07d (Google Chrome Framework -profile_destroyer.cc:120 ) ProfileDestroyer::~ProfileDestroyer() 0x000000010e8ec764 (Google Chrome Framework -callback.h:64 ) base::Timer::RunScheduledTask() 0x000000010e87dad8 (Google Chrome Framework -callback.h:64 ) base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask const&) 0x000000010e8a0b77 (Google Chrome Framework -message_loop.cc:405 ) base::MessageLoop::RunTask(base::PendingTask const&) 0x000000010e8a0e7b (Google Chrome Framework -message_loop.cc:414 ) base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) 0x000000010e8a140c (Google Chrome Framework -message_loop.cc:552 ) base::MessageLoop::DoDelayedWork(base::TimeTicks*) 0x000000010e8a3348 (Google Chrome Framework -message_pump_mac.mm:334 ) base::MessagePumpCFRunLoopBase::RunWork() 0x000000010e896229 (Google Chrome Framework + 0x017c8229 ) base::mac::CallWithEHFrame(void () block_pointer) 0x000000010e8a2d43 (Google Chrome Framework -message_pump_mac.mm:306 ) base::MessagePumpCFRunLoopBase::RunWorkSource(void*) 0x00007fffaa8184b0 (CoreFoundation + 0x000a74b0 ) __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 0x00007fffaa7f961c (CoreFoundation + 0x0008861c ) __CFRunLoopDoSources0 0x00007fffaa7f8b15 (CoreFoundation + 0x00087b15 ) __CFRunLoopRun 0x00007fffaa7f8513 (CoreFoundation + 0x00087513 ) CFRunLoopRunSpecific 0x00007fffa9d95fbb (HIToolbox + 0x00030fbb ) RunCurrentEventLoopInMode 0x00007fffa9d95df0 (HIToolbox + 0x00030df0 ) ReceiveNextEventCommon 0x00007fffa9d95c25 (HIToolbox + 0x00030c25 ) _BlockUntilNextEventMatchingListInModeWithFilter 0x00007fffa847fb78 (AppKit + 0x00046b78 ) _DPSNextEvent 0x00007fffa8b951c2 (AppKit + 0x0075c1c2 ) -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 0x00007fffa847453c (AppKit + 0x0003b53c ) -[NSApplication run] 0x000000010e8a3b4d (Google Chrome Framework -message_pump_mac.mm:665 ) base::MessagePumpNSApplication::DoRun(base::MessagePump::Delegate*) 0x000000010e8a318b (Google Chrome Framework -message_pump_mac.mm:238 ) base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*) 0x000000010e8bd360 (Google Chrome Framework -run_loop.cc:35 ) base::RunLoop::Run() 0x000000010e47df64 (Google Chrome Framework -chrome_browser_main.cc:2116 ) ChromeBrowserMainParts::MainMessageLoopRun(int*) 0x000000010dd0c8f3 (Google Chrome Framework -browser_main_loop.cc:981 ) content::BrowserMainLoop::RunMainMessageLoopParts() 0x000000010dd0eee1 (Google Chrome Framework -browser_main_runner.cc:155 ) content::BrowserMainRunnerImpl::Run() 0x000000010dd08c7b (Google Chrome Framework -browser_main.cc:46 ) content::BrowserMain(content::MainFunctionParams const&) 0x000000010e43855d (Google Chrome Framework -content_main_runner.cc:779 ) content::ContentMainRunnerImpl::Run() 0x000000010e437795 (Google Chrome Framework -content_main.cc:20 ) content::ContentMain(content::ContentMainParams const&) 0x000000010d0d13cb (Google Chrome Framework -chrome_main.cc:97 ) ChromeMain 0x0000000106633d49 (Google Chrome -chrome_exe_main_mac.c:85 ) main 0x0000000106633b33 (Google Chrome + 0x00000b33 ) start
,
Jan 21 2017
Interesting. I wonder if the two are related, or if it were a one-off crash. I can repro Dev Tools hanging every time I load that .cpuprofile up, but haven't had Chrome crash again at the same time. Maybe they are two seperate issues. Out of interest, is there any workaround you could suggest or alternative tool to load CPU profiles? I can no longer profile the performance of Node with this bug. Still hangs whenever I load a .cpuprofile up, even after restarts. I could try reinstalling Chrome but losing all data isn't ideal. Thanks!
,
Nov 2 2017
It doesn't crash for me, but the loaded profile looks corrupt. All the times are zero. Is that expected? |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ajha@chromium.org
, Jan 16 2017