New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 650545 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

frequent Aw Snap crashes in 55.0.2872.0 canary

Project Member Reported by dbloch@google.com, Sep 27 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2872.0 Safari/537.36

Steps to reproduce the problem:
1. Open some tabs and wait.

What is the expected behavior?
Tabs stay up.

What went wrong?
Since updating to 55.0.2872.0 this morning I've had 20 or 30 tabs go to "Aw Snap" state after some period of inactivity.  It isn't associated with any action I'm doing.

The crashes don't appear in chrome://crashes.

Crashed report ID: no

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? Yes yesterday

Chrome version: 55.0.2872.0  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
 
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 27 2016

Labels: Hotlist-Google

Comment 2 by dbloch@google.com, Sep 27 2016

I kept a console open in my Gmail tab waiting for it to crash, and it said this when it did:

RPC service (get_form_details) is enabled.
clients6.google.com/chat/v1/conversations/sendchatmessage?key=AIzaSyAfFJCeph-euFSwtmqFZi0kaKk-cZ5wufM&alt=protojson:1 POST https://clients6.google.com/chat/v1/conversations/sendchatmessage?key=AIzaSyAfFJCeph-euFSwtmqFZi0kaKk-cZ5wufM&alt=protojson net::ERR_QUIC_PROTOCOL_ERROR

Comment 3 by dbloch@google.com, Sep 28 2016

Only 3-4 crashes today.  May be fixed in 55.0.2873.0
Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Could you please confirm are you facing this issue on chrome latest canary M55-55.0.2875.0 ? 

Comment 5 by dbloch@google.com, Sep 29 2016

I haven't seen it at least since 55.0.2874.0.  Okay to close.

Thanks,
Dan
Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
As per comment #5 closing this issue. Please raise a new issue if you come across the similar one on latest chrome versions.

Sign in to add a comment