Issue metadata
Sign in to add a comment
|
NEEDS FEEDBACK: Various crashes in content editables on Android
Reported by
ryanac...@gmail.com,
May 26 2017
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: I'm not sure what the exact repro steps are, but we're seeing these crashes when typing in the Quora answer rich text editor after typing for awhile. We think that it might have something to do with the way we fix weird keyboard behaviors by watching the various text entry events. One crash was fixed by removing contenteditable=false on a div with an image in it, but we haven't been able to isolate other crashes. In that crash, it crashed when backspacing into that div when using a keyboard that has word replacement (wouldn't happen if a physical keyboard was attached). I've attached a microdump file, if someone could decode it into a stacktrace, I could help narrow down the issue. The microdump file is from a webview from our Android app but the crashes are occurring on the mobile web site too. What is the expected behavior? Not crashing What went wrong? Chrome crashes while typing into the editor. Did this work before? N/A Chrome version: 58.0.3029.83 Channel: stable OS Version: 7.1 Flash Version:
,
May 31 2017
To fix the bug, we need to have steps to reproduce the issue. Could you provide minimized HTML to reproduce your issue? I suggest using desktop Chrome for ease of reproduce. If it is happened only in Android, please try to change keyboard app. Sometime keyboard app call IME API with values what Chrome expected. Thanks!
,
May 31 2017
Hi, the issue Android only, and is reproducing with the official Google Keyboard, but won't reproduce if I use a hardware keyboard. It's not easy to reproduce quickly, I'm not sure what the exact trigger is. It'd be helpful if the microdump could be decoded, it would help me track down what might be the minimum repo steps.
,
Jun 1 2017
It seems microdump in #c1 doesn't have stack trace. We can't identify which function causes crash. Could you try to android emulator or attach gdb to chrome to get stack trace? Thanks!
,
Jun 14 2017
The NextAction date has arrived: 2017-06-14
,
Jun 15 2017
Mark "WontFix" since no step to reproduce in two weeks. Once you found reproduce steps, please reopen this issue. Thanks!
,
Jun 19 2017
I think this is fixed in the latest development branch. I built Chrome from source to try to debug this issue and don't see crashes anymore (continues to be an issue doing same tests in prod though). |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by cbiesin...@chromium.org
, May 30 2017