High Sierra: Chrome crashes when Accessibility > Invert Colors is toggled
Reported by
macsj...@gmail.com,
Oct 1 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome 2. Toggle "invert colors" (in system preferences) 3. Profit What is the expected behavior? What went wrong? Chrome crashed resoundingly. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.13.0 Flash Version:
,
Oct 2 2017
Can you please attach the recent report ID from chrome://crashes and/or the Apple Crash Log? Thanks in advance.
,
Oct 2 2017
Thanks, I am able to reproduce this somewhat reliably on YouTube. https://crash.corp.google.com/browse?q=reportid=%274416b831a8990f59%27 Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000014e295420 VM Regions Near 0x14e295420: shared memory 0000000118443000-0000000119848000 [ 20.0M] rw-/rw- SM=SHM --> MALLOC_NANO 0000600000000000-0000600001600000 [ 22.0M] rw-/rwx SM=PRV Application Specific Information: objc_msgSend() selector name: _systemSelectionColorChanged: Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00007fff681d4ea9 objc_msgSend + 41 1 com.apple.CoreFoundation 0x00007fff41885b5c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 2 com.apple.CoreFoundation 0x00007fff41885a4a _CFXRegistrationPost + 442 3 com.apple.CoreFoundation 0x00007fff41885792 ___CFXNotificationPost_block_invoke + 50 4 com.apple.CoreFoundation 0x00007fff41843570 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1664 5 com.apple.CoreFoundation 0x00007fff418426a3 _CFXNotificationPost + 595 6 com.apple.Foundation 0x00007fff43901477 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 7 com.apple.AppKit 0x00007fff3f2a274f -[NSApplication _axContrastChanged:] + 71 8 com.apple.CoreFoundation 0x00007fff41885b5c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 9 com.apple.CoreFoundation 0x00007fff41885a4a _CFXRegistrationPost + 442 10 com.apple.CoreFoundation 0x00007fff41885792 ___CFXNotificationPost_block_invoke + 50 11 com.apple.CoreFoundation 0x00007fff41843570 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1664 12 com.apple.CoreFoundation 0x00007fff418426a3 _CFXNotificationPost + 595 13 com.apple.Foundation 0x00007fff43901477 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 14 com.apple.CoreFoundation 0x00007fff41885b5c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 15 com.apple.CoreFoundation 0x00007fff41885aef ___CFXRegistrationPost_block_invoke + 63 16 com.apple.CoreFoundation 0x00007fff4188e52c __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12 17 com.apple.CoreFoundation 0x00007fff41870f43 __CFRunLoopDoBlocks + 275 18 com.apple.CoreFoundation 0x00007fff41870d08 __CFRunLoopRun + 3128 19 com.apple.CoreFoundation 0x00007fff4186fe43 CFRunLoopRunSpecific + 483 20 com.apple.HIToolbox 0x00007fff40b8f866 RunCurrentEventLoopInMode + 286 21 com.apple.HIToolbox 0x00007fff40b8f5d6 ReceiveNextEventCommon + 613 22 com.apple.HIToolbox 0x00007fff40b8f354 _BlockUntilNextEventMatchingListInModeWithFilter + 64 23 com.apple.AppKit 0x00007fff3ee8d44f _DPSNextEvent + 2085 24 com.apple.AppKit 0x00007fff3f622508 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044 25 com.google.Chrome.framework 0x00000001044e2ea0 __71-[BrowserCrApplication nextEventMatchingMask:untilDate:inMode:dequeue:]_block_invoke + chrome_browser_application_mac.mm:187 26 com.google.Chrome.framework 0x00000001048ecc2a base::mac::CallWithEHFrame(void () block_pointer) + 27 com.google.Chrome.framework 0x00000001044e2de4 -[BrowserCrApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + chrome_browser_application_mac.mm:192 28 com.apple.AppKit 0x00007fff3ee8225d -[NSApplication run] + 764 29 com.google.Chrome.framework 0x00000001048fd2ae base::MessagePumpNSApplication::DoRun(base::MessagePump::Delegate*) + message_pump_mac.mm:766 30 com.google.Chrome.framework 0x00000001048fbcac base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*) + message_pump_mac.mm:278 31 com.google.Chrome.framework 0x000000010491eb53 base::RunLoop::Run() + run_loop.cc:112 32 com.google.Chrome.framework 0x00000001044e8d46 ChromeBrowserMainParts::MainMessageLoopRun(int*) + chrome_browser_main.cc:1971 33 com.google.Chrome.framework 0x0000000103423e14 content::BrowserMainLoop::RunMainMessageLoopParts() + browser_main_loop.cc:1171 34 com.google.Chrome.framework 0x00000001034264d2 content::BrowserMainRunnerImpl::Run() + memory:2515 35 com.google.Chrome.framework 0x000000010341fe9c content::BrowserMain(content::MainFunctionParams const&) + browser_main.cc:46 36 com.google.Chrome.framework 0x000000010449f5d0 content::ContentMainRunnerImpl::Run() + content_main_runner.cc:686 37 com.google.Chrome.framework 0x0000000105dc2be4 service_manager::Main(service_manager::MainParams const&) + main.cc:469 38 com.google.Chrome.framework 0x000000010449ebb4 content::ContentMain(content::ContentMainParams const&) + content_main.cc:19 39 com.google.Chrome.framework 0x0000000102e3bcb8 ChromeMain + chrome_main.cc:0 40 com.google.Chrome 0x0000000101c93dd4 main + chrome_exe_main_mac.cc:174 41 libdyld.dylib 0x00007fff68dd1145 start + 1
,
Oct 2 2017
I can reliably reproduce this on 61.0.3163.100 but not on canary 63.0.3230.0 or beta 62.0.3203.38. I wonder if this is because 61 is using the old 10.10 SDK but 62+ are on 10.12.
,
Oct 2 2017
Issue 769285 has been merged into this issue.
,
Oct 2 2017
I tried running 62.0.3173.0, which was built with the 10.10 SDK, and 62.0.3174.0, which was built with the 10.12 SDK, and I wasn't able to repro on either. I also tried bisecting and wasn't able to reproduce it :/. I do think this is resolved by something in Chrome 62, which is currently on the beta channel. Could you try downloading that and seeing if the problem is resolved for you there?
,
Oct 2 2017
Hi, I tried the latest canary Version 63.0.3230.0 (Official Build) canary (64-bit) and it doesn't seem to crash.
,
Oct 2 2017
Thanks for testing. I tried some more to reproduce and got 100% reliable steps: 1. Go to YouTube and start watching a video, copy the URL 2. Open a new tab 3. Close the existing YouTube tab 4. Paste the URL in the new tab 5. Toggle inverted colors With those steps, I was able to bisect down to https://chromium.googlesource.com/chromium/src/+log/92466de58f6060945cea3c8cef01302c5e4eec3c..f5345de13668f0176b11126a7ae391dad5b4ad0f. So it definitely looks to be an SDK issue. I re-ran my test in #6 with the reliable steps and was able to verify as well: 62.0.3173.0 crashes and 62.0.3174.0 doesn't. Unfortunately the SDK change is not something we can easily merge to a release branch, so we may just have to wait until Chrome 62 is promoted to stable to have this fixed.
,
Oct 2 2017
Issue 748711 has been merged into this issue.
,
Oct 2 2017
This one is also pretty simple repro case: =========================================== 1. Launch Chrome and then "Command-Option-F5" 2. Select the option "Invert display color" to get the crash on any webpage Thank you!
,
Oct 2 2017
+erikchen since this was fixed by the SDK roll
,
Oct 6 2017
Issue 772436 has been merged into this issue.
,
Oct 18 2017
Has this been fixed in released v62 stable ? I have plenty of tabs open and I don't want to try to invert colors.
,
Oct 18 2017
Chrome 62 has started rolling out to stable channel, so this should be fixed in the next few days. https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html
,
Nov 6 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by macsj...@gmail.com
, Oct 1 2017