Issue metadata
Sign in to add a comment
|
chrome crash when type chinese simplified input
Reported by
remexl...@gmail.com,
Dec 11 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Switch to Chinese Simplified Input(mac default) 2. Type to url Chinese pinyin wait to select Chinese characters 3. Chrome will crash This is not happened every time. It may happened when you running chrome in a while, switch from other apps back to Chrome and do the search then will cause the crash. What is the expected behavior? Success select Chinese characters and continue input What went wrong? Chrome is crash Here is additional information as below: Process: Google Chrome [3307] Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome Identifier: com.google.Chrome Version: 62.0.3202.94 (3202.94) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Google Chrome [3307] Date/Time: 2017-12-11 09:42:09.104 -0500 OS Version: Mac OS X 10.12.3 (16D32) Report Version: 12 Time Awake Since Boot: 170000 seconds Time Since Wake: 28 seconds System Integrity Protection: enabled Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Application Specific Information: Crashing on exception: Unable to activate constraint with anchors <NSLayoutXAxisAnchor:0x610005c66c80 "NSRemoteView:0x61800013acc0.leading"> and <NSLayoutXAxisAnchor:0x61000607ba80 "_NSCandidateBarFunctionRowButton:0x7ffe1c7a64d0.leading"> because they have no common ancestor. Does the constraint or its anchors reference items in different view hierarchies? That's illegal. Application Specific Backtrace 1: 0 CoreFoundation 0x00007fff8b45de7b __exceptionPreprocess + 171 1 Google Chrome Framework 0x000000010d25d98b ChromeMain + 25184683 2 libobjc.A.dylib 0x00007fffa0047cad objc_exception_throw + 48 3 CoreFoundation 0x00007fff8b4dc99d +[NSException raise:format:] + 205 4 AppKit 0x00007fff895ddc18 -[NSCandidateListViewController _updateCollapsingStateConstraint] + 179 5 AppKit 0x00007fff895ddd49 -[NSCandidateListViewController updateViewConstraints] + 59 6 AppKit 0x00007fff88f6b636 -[NSView _updateConstraintsForSubtreeIfNeededCollectingViewsWithInvalidBaselines:] + 828 7 AppKit 0x00007fff89787f4b __46-[NSView _updateConstraintsForSubtreeIfNeeded]_block_invoke + 49 8 Foundation 0x00007fff8ce23b7b -[NSISEngine withBehaviors:performModifications:] + 155 9 AppKit 0x00007fff88ee4ede -[NSView(NSConstraintBasedLayout) _withAutomaticEngineOptimizationDisabled:] + 70 10 AppKit 0x00007fff89787ed6 -[NSView _updateConstraintsForSubtreeIfNeeded] + 157 11 AppKit 0x00007fff88f6b2dd -[NSView updateConstraintsForSubtreeIfNeeded] + 45 12 Foundation 0x00007fff8ce23b7b -[NSISEngine withBehaviors:performModifications:] + 155 13 AppKit 0x00007fff88ee4ede -[NSView(NSConstraintBasedLayout) _withAutomaticEngineOptimizationDisabled:] + 70 14 AppKit 0x00007fff89951cfa -[NSTouchBarItem _itemViewMinSize:maxSize:preferredSize:] + 866 15 Foundation 0x00007fff8ce23b7b -[NSISEngine withBehaviors:performModifications:] + 155 16 AppKit 0x00007fff893b3f7c -[NSTouchBarItemView minSize] + 117 Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: OS X 10.12.3 Flash Version:
,
Dec 11 2017
No, it is not a touchBar crash. The whole chrome will crash and raise this exception. It is happened when: 1. To Type Chinese characters in Chrome URL bar 2. To type Chinese characters in web page's input or textarea 3. To type Chinese characters in Slack(I think Chromium inside)
,
Dec 12 2017
Tested the issue on Mac OS 10.12.6 using chrome M62 #62.0.3202.94 and M63 #63.0.3239.84 and followed below steps: 1. Switched the mac keyboard language to chinese simplified 2. Typed in the url bar and chinese texts popped up and couldn't see any crash. Attached screencast for reference. @ remexllee-- Could you please check attached screencast and confirm us if we have missed any steps in reproducing the issue and also please try in latest stable in a fresh chrome profile without any extensions and flags enabled and update us with your observations along with the crash id from chrome://crashes. Thanks!
,
Dec 12 2017
,
Dec 16 2017
Hi hdodda Thanks for this video, looks all steps are includes. The issue usually happened when running chrome in a while like half day, then when switch from other apps to Chrome. I had try to disable all extensions of my chrome and looks it is not crash again. But I would test a little bit more time. I will closed this ticket if it never happen again.
,
Dec 16 2017
Thank you for providing more feedback. Adding requester "hdodda@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
,
Dec 19 2017
remexllee@ as per comment #5 could you confirm whether the crash is happening again ?
,
Jan 5 2018
[mac bug triage] Can you provide a server crash id for this crash from chrome://crashes?
,
Jan 5 2018
sure, this is the last time my chrome crash with this error: Local Crash ID 8006ad9a-8ae8-4992-a9f4-8d1e364c1177 Crash report captured on Wednesday, December 27, 2017 at 3:40:50 PM was not uploaded
,
Jan 5 2018
Thank you for providing more feedback. Adding requester "kkaluri@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
,
Jan 8 2018
remexllee@ -- Thanks for providing, could you please share the 'Crash Report ID' from chrome://crashes, which will be in below format. Example: Crash Report ID 1561e3079400a85d Thanks!
,
Mar 5 2018
Mac triage: we have exactly one crash that looks similar to this, with id bd9958b24062d9e8, from M62. Since we don't have any repro steps either, this is WontFix. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by meh...@chromium.org
, Dec 11 2017