Issue metadata
Sign in to add a comment
|
Chrome: Crash Report - v8::String::Utf8Value::Utf8Value
Reported by
julien.c...@gmail.com,
Apr 19 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36 Steps to reproduce the problem: 1. Create a apache/cordova empty project 2. Install ripple as explained in that blog: https://www.raymondcamden.com/2013/11/05/Ripple-is-Reborn/ 3. Run the apache/cordova app with ripple thru the command line interface. What is the expected behavior? Ripple should work. What went wrong? The "aw snapp" message is thrown on the user screen. Crashed report ID: aw snapp message How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? Yes In previous chrome version 49.x.x.x.x Chrome version: 50.0.2661.75 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0 It worked well until previous stable chrome version 49.x.x.x - but since it is impossible to get my hands on the previous chrome version, I am stuck with version 50 that cannot function well with ripple.
,
Apr 20 2016
julien.castrie@, can you please navigate to chrome://crashes and provide the crash ID so that we can investigate this further ?
,
Apr 21 2016
crash id is: 63f9e19200000000 (69b368a0-412b-46b9-a850-04c8820ca34c)
,
Apr 21 2016
Thank you for providing more feedback. Adding requester "pucchakayala@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
,
Apr 22 2016
Hi, will that be investigated further or (if not) could you provide me access to former Chrome version (anterior to 50.0.2661.75)?
,
Apr 22 2016
This crash started spiking in M48, below are crash rate in stable channels. 50.0.2661.75 40.68% 3586 49.0.2623.112 0.83% 73 48.0.2564.116 2.51% 221 Link to the builds which introduced the crash. https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27v8%3A%3AString%3A%3AUtf8Value%3A%3AUtf8Value%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000 Routing to V8 team for triaging.
,
Apr 28 2016
This is fixed on M51, and due to the nature of the changes a backmerge is considered infeasible. In the meantime (probably roughly four weeks), you can use the Beta, Dev, or Canary channel of Chrome, which all contain the fix already. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Apr 20 2016