Add "v8::internal::IncrementalMarking::Step" crash signature to "Memory corruption (v8)" bucket |
||||
Issue descriptionThis is a follow-up of crbug.com/635779 As explained in https://bugs.chromium.org/p/chromium/issues/detail?id=635779#c19 the "v8::internal::IncrementalMarking::Step" crashes belong to "Memory corruption (v8)" bucket. "Memory corruption (v8)" example: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20product.version%3D%2752.0.2743.75%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27Memory%20corruption%20(v8)%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.component%3D%27src%2Fv8%2Fsrc%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27Memory%20corruption%20(v8)%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0 "v8::internal::IncrementalMarking::Step" example: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27v8%3A%3Ainternal%3A%3AIncrementalMarking%3A%3AStep%27%20AND%20product.version%3D%2755.0.2858.0%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0 Note that the stack traces are almost the same.
,
Dec 3 2016
Users experienced this crash on the following builds: Win Beta 55.0.2883.75 - 9.87 CPM, 855 reports, 779 clients (signature v8::internal::IncrementalMarking::Step) Mac Canary 57.0.2939.0 - 1.36 CPM, 3 reports, 3 clients (signature v8::internal::IncrementalMarking::Step) Android Dev 56.0.2924.10 - 1.08 CPM, 13 reports, 7 clients (signature v8::internal::IncrementalMarking::Step) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Dec 19 2016
This crash reappeared in latest beta version as below 57.0.2946.0 0.30% 4 from 4 unique client Ids - Prev dev 56.0.2924.28 1.98% 26 from 4 unique client Ids - Beta 52.0.2743.116 25.00% 328 52.0.2743.82 3.43% 45 52.0.2743.41 0.46% 6 52.0.2743.33 0.08% 1 51.0.2704.106 10.90% 143 51.0.2704.103 1.14% 15 51.0.2704.84 1.30% 17 Link to the builds: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Linux%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27v8%3A%3Ainternal%3A%3AIncrementalMarking%3A%3AStep%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000
,
Jan 3 2017
Just to update the latest behavior of the issue, still crashes observed on latest beta and dev channels. No crashes observed on chrome latest stable and canary channels. 56.0.2924.28 8.66% 102 - Beta 57.0.2950.4 1.61% 19 - Dev https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Linux%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27v8%3A%3Ainternal%3A%3AIncrementalMarking%3A%3AStep%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000
,
Jan 10 2017
,
Jan 10 2017
for mis-classification and requests to tune the magic signature please file an internal bug (Chrome > ChromeCrash > Backend) and cc ivanpe@
,
Jan 12 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by sheriffbot@chromium.org
, Dec 1 2016