New issue
Advanced search Search tips

Issue 668809 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: ----
Type: Bug



Sign in to add a comment

Pinyin input crash

Reported by slei.cas...@gmail.com, Nov 26 2016

Issue description



VULNERABILITY DETAILS
when using pinin input source, just type afl in address bar, chrome will crash.

VERSION
Version 54.0.2840.98 (64-bit)
Operating System: OSX 10.10.3

REPRODUCTION CASE


FOR CRASHES, PLEASE INCLUDE THE FOLLOWING ADDITIONAL INFORMATION
browser


 
Labels: Needs-Feedback
I cannot reproduce this on Chrome Stable for Mac. Can you please give more detailed (step by step) instructions on how to trigger this crash, including how you enabled the Pinyin input source, whether it was Simplified or Traditional, and whether or not you pushed enter or any other keys?
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
Summary: Pinyin input crash (was: Security: Others)
Removing this from the security queue.

Comment 3 by ajha@chromium.org, Dec 6 2016

Components: UI>Input>Text>IME
Labels: M-54 OS-Mac
It's Simplified piyin, just type afl. When you push l, chrome would crash.You can try multi times, I tried three times to trigger this crash.
Can you provide some "Server ID"s from chrome://crashes after this happens?
I only see Crash ID. Do you mean that?
Project Member

Comment 7 by sheriffbot@chromium.org, Dec 15 2016

Labels: -Needs-Feedback Needs-Review
Owner: dominickn@chromium.org
Thank you for providing more feedback. Adding requester "dominickn@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review
Owner: ----
The crash ID is what we'd like, yes. Please paste it in here so the Mac team can investigate further.

Comment 9 by tapted@chromium.org, Dec 21 2016

Labels: Needs-Feedback
I can't reproduce in macOS 10.12.2 Sierra. (note: an OS upgrade may help 10.10.3 is from April, 2015 - 10.10.5 is available, and also 10.12, and these are typically free upgrades).

If you only see `Crash ID` in chrome://crashes it hasn't been reported. There's a checkbox at chrome://settings "Automatically send usage statistics and crash reports to Google". Or I think you can even select one to upload now.

If you can send us a Server ID (they look something like 0f20cb4080000000), we can diagnose this further. Let us know if upgrading the OS helps, too.
Crash ID cc60067f-1cdf-4ace-ba55-3634f8041edf

Crash report captured on Friday, December 23, 2016 at 2:35:31 PM was not uploaded
What you copy/pasted says "was not uploaded" - can you open ~/Library/Application Support/Google/Chrome/Crashpad/ in the Finder and see if there are any crash reports in the subfolders (new, pending)? ~ being shorthand for your home folder.
Project Member

Comment 12 by sheriffbot@chromium.org, Jan 23 2017

Labels: -Needs-Feedback Needs-Review
Owner: tapted@chromium.org
Thank you for providing more feedback. Adding requester "tapted@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-Feedback
Owner: ----
#c10 - that's a Crash ID. Please send us a Server ID per #c9. There should be a "Send now" link at chrome://crashes that will generate a Server ID. 
Status: WontFix (was: Unconfirmed)
No response from reporter in over 30 days, so closing out. c#10 - if you're able to provide the info requested in c#9 we can open this back up.

Sign in to add a comment