Streaming ServiceWorker test app crashes Chrome 55 tabs (but not 54 or 53)
Reported by
gwi...@wikimedia.org,
Oct 3 2016
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2873.0 Safari/537.36 Steps to reproduce the problem: 1. Follow a couple of links starting at https://swproxy.wmflabs.org/wiki/Main_Page. Re-loading the same page also triggers the problem. What is the expected behavior? Pages load, no crash. What went wrong? Tab crashes with "aw snap" about every 10th navigation. Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? Yes Chrome 53, Chrome 54 Chrome version: 55.0.2873.0 Channel: dev OS Version: Debian unstable Flash Version: Shockwave Flash 23.0 r0 Happens in Chrome 55 on Linux and Android.
,
Oct 7 2016
Still happens reliably with .2882.4 on Android, haven't tested on Debian yet. Example crash ID from Android is 8073dc9d00000000.
,
Oct 7 2016
Desktop (Debian) crash id: 4ade998b00000000
,
Oct 10 2016
Looks like a null pointer dereference: [ 3749.144566] ServiceWorker T[8604]: segfault at 0 ip 000055f2c401bad1 sp 00007f963766e3d0 error 4 in chrome[55f2bf926000+64e2000]
,
Oct 18 2016
Thank you for providing more feedback. Adding requester "brajkumar@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
,
Oct 24 2016
Still reproducible with Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2897.0 Safari/537.36.
,
Dec 1 2016
As per provided report ID in comment #3, This crash is last seen on #55.0.2882.0 with 4 instances. No crashes observed later. gwicke@ Could you please confirm that are you still seeing this issue on chrome latest Dev #56.0.2924.10?
,
Dec 16 2016
Still happens at the same frequency with 57.0.2946.0: 96a6bf0080000000, 3a8f981300000000
,
Dec 26 2016
Thank you for providing more feedback. Adding requester "brajkumar@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
,
Jan 20 2017
This issue first seen on #57.0.2946.0, Below link gives in details of the number of instances in which the crash has occurred for associated builds: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Linux%27%20%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27blink%3A%3ABodyStreamBuffer%3A%3AprocessData%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D 57.0.2979.0 14.29% 1 57.0.2946.0 85.71% 6 As per the crash server this crash is seen only on one client ID, Might be specific to system hardware or OOM crash. Since there is know consistent steps available to reproduce this issue, Adding Needs-Triage label for further investigation.
,
Feb 14 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by brajkumar@chromium.org
, Oct 7 2016Labels: Needs-Feedback