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

Issue 670336 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Clicking status area crashes chrome

Reported by malcolml...@gmail.com, Dec 1 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 9000.10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.9 Safari/537.36
Platform: 9000.10.0 (Official Build) dev-channel peppy

Steps to reproduce the problem:
1. Click on status area

What is the expected behavior?
Opening the status area

What went wrong?
The browser and display crash, and recover ~5s later.

Crashed report ID: No

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? Yes Last version

Chrome version: 56.0.2924.9  Channel: dev
OS Version: 9000.10.0
Flash Version: Shockwave Flash 23.0 r0

The crash is not showing up in chrome://crashes with the privacy option enabled.
 
I tested enabling and disabling addons, and it seems to be related to the Cisco AnyConnect extension.
Cc: dhadd...@chromium.org
Components: UI>Shell>StatusArea
Owner: tbuck...@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: tdander...@chromium.org tbuck...@chromium.org varkha@chromium.org steve...@chromium.org
Labels: -Pri-2 Proj-MaterialDesign-CrOS M-56 Pri-1
Owner: varkha@chromium.org
I haven't heard of any similar crashes so this may be fixed (user was on a dev build).

@varkha can you double-check that the system menu works properly with 3rd-party VPN extensions? stevenjb@ has made some sample ones.
Owner: steve...@chromium.org
malcolmlorber@ can you try this out on the latest version of m-56 (beta channel) and make sure that the new 'material design' style system menu is enabled? (The ash-md flag should be set to "Default" on about:flags). If this is still reproducable can you double check about:crashes to see if a crash ID has been generated?

stevenjb@ can you provide any guidance regarding #4?
Labels: Needs-Feedback
Owner: tdander...@chromium.org
Without a crash ID it is hard to say for sure, but I suspect it may have been this:

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_ChromeOS%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27ash%3A%3AStatusAreaWidget%3A%3AIsNextVisibleTrayToLogout%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D

Which has not shown up since 56.0.2924.26 (Beta channel is currently 	56.0.2924.87).

I would suggest closing this as WontFix, pending confirmation by  malcolmlorber@,

I did also try this with a third party VPN installed on ToT and it seems fine. (also I shared a VPN Demo folder in Drive with tdanderson@ and varkha@)

malcolmlorber@, friendly ping - can you still reproduce this issue on the latest dev or beta channels? If so please let us know which and indicate the chrome version you're using.
Status: WontFix (was: Assigned)
Marking as WontFix. malcolmlorber@ or anyone else, please file a new issue if you still observe this issue.

Sign in to add a comment