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

Issue 761300 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome opens, then slows down and stops responding

Reported by c.sc...@albion.co.uk, Sep 1 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13) AppleWebKit/604.1.38 (KHTML, like Gecko) Version/11.0 Safari/604.1.38

Steps to reproduce the problem:
1. Run Chrome on its own without any other apps running
2. Chrome lets me open a webpage but after 1-2 minutes, slows down and stops responding. I wait 5-10 minutes before deciding to force quit. Only the loading colour wheel showing whilst waiting.
3. Delete chrome app, clear caches and App Support files. Reinstall chrome from a freshly downloaded app.
4. Same steps as number 1 and 2.

What is the expected behavior?

What went wrong?
I believe chrome to be tripping up on something that starts to load after the browser has been running for a short while. I do have a few extensions running which may be the cause but it was working fine until I installed Beta Update 8 last night.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes OSX High Sierra Beta 7

Chrome version: <Copy from: 'about:version'>  Channel: beta
OS Version: OS X 10.13
Flash Version: 17A358a

I am not a dev at all so if you need more technical details, it might be difficult for me to help. Let me know either way.
 
Cc: shrike@chromium.org
Labels: Hotlist-HighSierra Needs-Feedback
c.scott@, Thank you for the report. Can you please let me know the chrome version#? Also please record a trace (https://www.chromium.org/developers/how-tos/submitting-a-performance-bug) if it's reproducible consistently.
Version Number is 60.0.3112.113.

Weirdly when I recorded the trace, Chrome did not crash. I did the usual startup that makes chrome crash but for some reason it didn't this time.

I opened the trace as soon as Chrome started to try and record it crashing but I carried on as usual (Gmail, Sheets etc) and no problems.

No idea why but it would still be good to see whats going on.

trace_Chrome_Crash.json.gz
13.4 MB Download
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 4 2017

Cc: manoranj...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "manoranjanr@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
Cc: pnangunoori@chromium.org
Labels: Needs-Feedback
@c.scott -- Thanks for providing reply. Could you please provide us the 'Crash Report ID' by navigating to 'chrome://crashes/'. And could you also please let us know if the crash is observed consistently. 

Thanks in advance.
The plot has thickened. Since I followed the trace recording chrome has magically been working fine. Really unusual.

Anyway here are the crash reports:

Aug 26th 2017: Local Crash ID 744aba30-b1f0-4e34-945b-0d63f7e197f5
Aug 18th 2017: Local Crash ID 26f6a850-fa07-4626-96de-bdc2e942ac15
Aug 15th 2017: Local Crash ID 31a1a7b8-10d6-4ab2-8548-9f9a8a7f5fc0

I resorted back to safari whilst chrome stopped working. After I ran the trace recording Chrome has worked without issue. 
Project Member

Comment 6 by sheriffbot@chromium.org, Sep 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pnangunoori@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
Labels: Needs-Feedback
@c.scott -- Could you please provide us the 'Crash Report ID' by navigating to 'chrome://crashes/' (not the Local Crash ID).

Please refer the attachment, highlighting the "Crash Report ID".

Thanks in advance.
761300.png
16.9 KB View Download

Comment 8 Deleted

Project Member

Comment 9 by sheriffbot@chromium.org, Sep 7 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "pnangunoori@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
Labels: Needs-Milestone Needs-Feedback
c.scott@,
Somehow C#8 has been deleted, Could you please respond to C#7 to triage this issue further from TE end.

Thanks in advance..!
Please see attached screenshot.
Screen Shot 2017-09-08 at 11.36.41.png
86.0 KB View Download
Project Member

Comment 12 by sheriffbot@chromium.org, Sep 8 2017

Cc: jmukthavaram@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "jmukthavaram@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
Quick update from my end. I had the same issue for 2 days and then Chrome went back to working. i also have live stats about my mac running (iStat Pro) and at one point, with only 6 tabs open and notes, the CPU temp peaked at 103 degrees centigrade! I checked my CPU usage and Chrome was the app using everything. 

Every so often Chrome will stop responding for a minute or two and then run fine again. I work for an Apple Service Centre and got my mac checked (diagnostics etc) and there is nothing wrong with my mac. The tech guys even opened it up to check for debris or loose connections but nothing out of the norm. Im not sure if this helps at all?
Cc: spqc...@chromium.org
The crash logs in c#8 have the following backtrace (a fullscreen issue). I'm not sure that the slowness would be related to fullscreen or to this crash.

c.scott@albion.co.uk - the next time Chrome stops responding, please use the Sample command in the Activity Monitor app to take a sample and attach the output to this bug


0x00000001052a6664	(AppKit + 0x0036c664 )	-[NSApplication _crashOnException:]
0x00000001052a654b	(AppKit + 0x0036c54b )	-[NSApplication reportException:]
0x0000000105390cb7	(AppKit + 0x00456cb7 )	uncaughtErrorProc
0x0000000108dbf052	(CoreFoundation + 0x0019d052 )	__handleUncaughtException
0x0000000108593e9c	(libobjc.A.dylib + 0x00016e9c )	_objc_terminate()
0x000000010a3d27c8	(libc++abi.dylib + 0x0001d7c8 )	std::__terminate(void (*)())
0x000000010a3d2477	(libc++abi.dylib + 0x0001d477 )	__cxa_rethrow
0x0000000108592138	(libobjc.A.dylib + 0x00015138 )	objc_exception_rethrow
0x0000000105af3496	(AppKit + 0x00bb9496 )	-[NSWindow(NSFullScreen) _didExitFullScreen]
0x00000001055fd99d	(AppKit + 0x006c399d )	-[_NSWindowExitFullScreenTransitionController doAfterExitFullScreen]
0x00000001058e3099	(AppKit + 0x009a9099 )	-[_NSExitFullScreenTransitionController _doAfterExitFullScreen]
0x0000000105aa4716	(AppKit + 0x00b6a716 )	-[_NSFullScreenSpace(Transitions) interruptTransitions]
0x0000000105af66f6	(AppKit + 0x00bbc6f6 )	-[NSWindow(NSFullScreen) _doFullScreenCleanupForOrderOut]
0x000000010584e4f5	(AppKit + 0x009144f5 )	-[NSWindow _reallyDoOrderWindowOutRelativeTo:findKey:forCounter:force:isModal:]
0x00000001050a8d8f	(AppKit + 0x0016ed8f )	-[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:]
0x00000001050a7c04	(AppKit + 0x0016dc04 )	-[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:]
0x00000001050a7a6a	(AppKit + 0x0016da6a )	-[NSWindow orderWindow:relativeTo:]
0x000000010584b9a1	(AppKit + 0x009119a1 )	-[NSWindow _finishClosingWindow]
0x00000001051ed1ef	(AppKit + 0x002b31ef )	-[NSWindow _close]
0x00000001111d33b0	(Google Chrome Framework -callback.h:91 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x00000001111f9e5a	(Google Chrome Framework -message_loop.cc:409 )	base::MessageLoop::RunTask(base::PendingTask*)
0x00000001111fa254	(Google Chrome Framework -message_loop.cc:420 )	base::MessageLoop::DeferOrRunPendingTask(base::PendingTask)
0x00000001111fa432	(Google Chrome Framework -message_loop.cc:508 )	base::MessageLoop::DoWork()
0x00000001111fd889	(Google Chrome Framework -message_pump_mac.mm:421 )	base::MessagePumpCFRunLoopBase::RunWork()
0x00000001111ee499	(Google Chrome Framework + 0x01b23499 )	base::mac::CallWithEHFrame(void () block_pointer)
0x00000001111fd1ae	(Google Chrome Framework -message_pump_mac.mm:397 )	base::MessagePumpCFRunLoopBase::RunWorkSource(void*)
0x0000000108cc5890	(CoreFoundation + 0x000a3890 )	__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
0x0000000108d7f33b	(CoreFoundation + 0x0015d33b )	__CFRunLoopDoSource0
0x0000000108ca838f	(CoreFoundation + 0x0008638f )	__CFRunLoopDoSources0
0x0000000108ca780c	(CoreFoundation + 0x0008580c )	__CFRunLoopRun
0x0000000108ca7072	(CoreFoundation + 0x00085072 )	CFRunLoopRunSpecific
0x0000000107682875	(HIToolbox + 0x0002f875 )	RunCurrentEventLoopInMode
0x00000001076825e5	(HIToolbox + 0x0002f5e5 )	ReceiveNextEventCommon
0x0000000107682363	(HIToolbox + 0x0002f363 )	_BlockUntilNextEventMatchingListInModeWithFilter
0x0000000104f7bc0e	(AppKit + 0x00041c0e )	_DPSNextEvent
0x000000010571074f	(AppKit + 0x007d674f )	-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
0x0000000110d6810f	(Google Chrome Framework -chrome_browser_application_mac.mm:187 )	__71-[BrowserCrApplication nextEventMatchingMask:untilDate:inMode:dequeue:]_block_invoke
0x00000001111ee499	(Google Chrome Framework + 0x01b23499 )	base::mac::CallWithEHFrame(void () block_pointer)
0x0000000110d68053	(Google Chrome Framework -chrome_browser_application_mac.mm:186 )	-[BrowserCrApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
0x0000000104f70a0b	(AppKit + 0x00036a0b )	-[NSApplication run]
0x00000001111fe0bd	(Google Chrome Framework -message_pump_mac.mm:749 )	base::MessagePumpNSApplication::DoRun(base::MessagePump::Delegate*)
0x00000001111fcabb	(Google Chrome Framework -message_pump_mac.mm:141 )	base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*)
0x000000011121f052	(Google Chrome Framework -run_loop.cc:111 )	base::RunLoop::Run()
0x0000000110d6df84	(Google Chrome Framework -chrome_browser_main.cc:1963 )	ChromeBrowserMainParts::MainMessageLoopRun(int*)
0x000000010fbf75c3	(Google Chrome Framework -browser_main_loop.cc:1184 )	content::BrowserMainLoop::RunMainMessageLoopParts()
0x000000010fbf9e01	(Google Chrome Framework -browser_main_runner.cc:142 )	content::BrowserMainRunnerImpl::Run()
0x000000010fbf350b	(Google Chrome Framework -browser_main.cc:46 )	content::BrowserMain(content::MainFunctionParams const&)
0x0000000110d2414a	(Google Chrome Framework -content_main_runner.cc:705 )	content::ContentMainRunnerImpl::Run()
0x00000001126105e1	(Google Chrome Framework -main.cc:469 )	service_manager::Main(service_manager::MainParams const&)
0x0000000110d23523	(Google Chrome Framework -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x000000010f6ce9c7	(Google Chrome Framework -chrome_main.cc:109 )	ChromeMain
0x00000001032b2dc3	(Google Chrome -chrome_exe_main_mac.cc:86 )	main
0x000000010a545154	(libdyld.dylib + 0x00001154 )	start
Cc: sdy@chromium.org
Labels: -Pri-2 ReleaseBlock-Beta M-62 Pri-1
Owner: spqc...@chromium.org
Status: Assigned (was: Unconfirmed)
Over to spqchan for intersection of High Sierra + Fullscreen. 
Labels: -M-62 M-63
This issue is existing from M60, so tagging with latest Dev milestone.
Friendly ping!
spqchan@,
Could you please take a look into this issue as per C#15,as it is marked as release block beta.
Thanks in advance..!!
Hi All, thanks for all your advice and support. Since the last message I sent i have not had any crashes or issues. I did have a very annoying issue whereby when Youtube (as an example) was full screen, after a short amount of time the video window would go blank but the video would still play. Sound would continue as normal. To get the video back on screen I would have click the Youtube window.
The GM release of High Sierra has just been made available to me for download so I will continue with the update and let you know how I get on (unless you would suggest otherwise, Chrome is really important for me as its what I do all my work on). 

Also on a side note, I have no idea how run this code within Activity Monitor. Sorry for the lack of knowledge on this part.

Comment 19 by ajha@chromium.org, Sep 26 2017

Friendly ping for an update as per C#18 and the behavior of this post High Sierra update.

Comment 20 by ajha@chromium.org, Oct 3 2017

If this is no longer an issue, shall we remove the blocker label from here?
Cc: ligim...@chromium.org
spqchan@,
Gentle ping to get an update on this issue as we have scheduled beta release on 10/11 and this is marked as Beta blocker .
Thanks..!
M63 is branching on this Thursday (10/12) and M63 beta promotion is coming very soon. Your bug is labelled as Beta ReleaseBlock, pls make sure to land the fix ASAP. Thank you.
Status: Started (was: Assigned)
Sorry for the late update, I've started looking into this
Status: WontFix (was: Started)
As per comment #18. Feel free to reopen if otherwise

Sign in to add a comment