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

Issue 716397 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Chrome Crash is seen on clicking 'Network info' icon and on 'Previous menu' in Uber Tary

Project Member Reported by mmanchala@chromium.org, Apr 28 2017

Issue description

Chrome Version: 60.0.3080.3/9501.0.0 dev channel Kip,Balze and Paine
OS: Chrome

Pre-Condition:  Make sure Browser window  should be minimized or closed.

What steps will reproduce the problem?
(1)Sign into User -> Click on Uber Tray
(2)Select Network option ->Click on 'Network info' icon -> Now click on 'Previous menu' arrow
(3)Now move the cursor and observe Chrome Crash (Please refer video)

Expected: No Chrome Crash should be seen on clicking 'Network info' icon 
Actual: Instead chrome Crash is seen

This is Regression issue as same is working fine in 58.0.3029.89/9334.58.0 Beta-channel Candy device

@tbuckley: Please confirm the Issue.

Below is the Crash id:
a1cf3f6e80000000

Stack Trace:

Thread 0 CRASHED [SIGSEGV @ 0x00000000 ] MAGIC SIGNATURE THREAD
Stack Quality97%Show frame trust levels
0x000060b96e6de7cc	(chrome + 0x048417cc )	ash::SystemTray::GetSystemBubble()
0x000060b96e786e51	(chrome + 0x048e9e51 )	non-virtual thunk to ash::tray::NetworkStateListDetailedView::InfoBubble::OnMouseExited(ui::MouseEvent const&)
0x000060b96d249b7f	(chrome + 0x033acb7f )	ui::EventDispatcher::ProcessEvent(ui::EventTarget*, ui::Event*)
0x000060b96d2499e7	(chrome + 0x033ac9e7 )	ui::EventDispatcherDelegate::DispatchEvent(ui::EventTarget*, ui::Event*)
0x000060b96dec2115	(chrome + 0x04025115 )	views::internal::RootView::NotifyEnterExitOfDescendant(ui::MouseEvent const&, ui::EventType, views::View*, views::View*)
0x000060b96dec1cf3	(chrome + 0x04024cf3 )	views::internal::RootView::OnMouseMoved(ui::MouseEvent const&)
0x000060b96de9aa9e	(chrome + 0x03ffda9e )	views::Widget::OnMouseEvent(ui::MouseEvent*)
0x000060b96d249b7f	(chrome + 0x033acb7f )	ui::EventDispatcher::ProcessEvent(ui::EventTarget*, ui::Event*)
0x000060b96d2499e7	(chrome + 0x033ac9e7 )	ui::EventDispatcherDelegate::DispatchEvent(ui::EventTarget*, ui::Event*)
0x000060b96fbc5cfd	(chrome + 0x05d28cfd )	ui::EventProcessor::OnEventFromSource(ui::Event*)
0x000060b96d24a45c	(chrome + 0x033ad45c )	ui::EventSource::SendEventToSink(ui::Event*)
0x000060b96e6a07a6	(chrome + 0x048037a6 )	ash::AshWindowTreeHostPlatform::DispatchEvent(ui::Event*)
0x000060b96d24afd6	(chrome + 0x033adfd6 )	ui::DispatchEventFromNativeUiEvent(void* const&, base::Callback<void (ui::Event*), (base::internal::CopyMode)1, (base::internal::RepeatMode)1>)
0x000060b96b05d0d6	(chrome + 0x011c00d6 )	ui::DrmWindowHost::DispatchEvent(void* const&)
0x000060b96b05d159	(chrome + 0x011c0159 )	non-virtual thunk to ui::DrmWindowHost::DispatchEvent(void* const&)
0x000060b96d2262f5	(chrome + 0x033892f5 )	ui::PlatformEventSource::DispatchEvent(void*)
0x000060b96d422cd4	(chrome + 0x03585cd4 )	ui::EventFactoryEvdev::DispatchMouseMoveEvent(ui::MouseMoveEventParams const&)
0x000060b96ad6c74c	(chrome + 0x00ecf74c )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000060b96ad62d15	(chrome + 0x00ec5d15 )	base::MessageLoop::RunTask(base::PendingTask*)
0x000060b96ad63e0e	(chrome + 0x00ec6e0e )	base::MessageLoop::DoWork()
0x000060b96c96643a	(chrome + 0x02ac943a )	base::MessagePumpLibevent::Run(base::MessagePump::Delegate*)
0x000060b96c9833fd	(chrome + 0x02ae63fd )	base::RunLoop::Run()
0x000060b96c5ffdfd	(chrome + 0x02762dfd )	ChromeBrowserMainParts::MainMessageLoopRun(int*)
0x000060b96b3296b0	(chrome + 0x0148c6b0 )	content::BrowserMainLoop::RunMainMessageLoopParts()
0x000060b96b32bf9c	(chrome + 0x0148ef9c )	content::BrowserMainRunnerImpl::Run()
0x000060b96b324fd5	(chrome + 0x01487fd5 )	content::BrowserMain(content::MainFunctionParams const&)
0x000060b96c5b81c7	(chrome + 0x0271b1c7 )	content::ContentMainRunnerImpl::Run()
0x000060b96db1099a	(chrome + 0x03c7399a )	service_manager::Main(service_manager::MainParams const&)
0x000060b96c5b7171	(chrome + 0x0271a171 )	content::ContentMain(content::ContentMainParams const&)
0x000060b96ae31c1c	(chrome + 0x00f94c1c )	ChromeMain
0x00007841345fc815	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x000060b96ae31a48	(chrome + 0x00f94a48 )	_start
0x00007ffdefe031c7		

 
Actual_Crash.mp4
6.5 MB View Download
Attaching expected Video
Expected.mp4
8.4 MB View Download
Cc: songsuk@chromium.org pucchakayala@chromium.org twreid@chromium.org

Comment 3 by ricea@chromium.org, May 1 2017

Components: -Blink>Network
The component Blink>Network should not be on this issue. Blink>Network is for issues with the web platform network APIs.
Cc: tbuck...@chromium.org
Labels: -ReleaseBlock-Beta ReleaseBlock-Stable Proj-MaterialDesign-CrOS
Owner: est...@chromium.org
FYI during a bisect of an unrelated issue, I noticed that this does not reproduce at 6add17253a0318bb3360c33de735f1f0ab3b8cd2 (#458554).
Status: WontFix (was: Assigned)
Marking as WontFix, looks like this was fixed elsewhere.
Status: Assigned (was: WontFix)
As per comment # 5 checked Issue in Latest M-60 build #60.0.3089.0/9531.0.0 dev-channel Candy and able to repro the Issue.
Very strange. On Samus 60.0.3086.0 canary I cannot repro this. As soon as I click the back arrow, the network info tooltip disappears.
I reproduced once, but not sure how. Playing around with it for a bit got it stuck, even though most of the time it works as tbuckley describes. I'll look into it.
Status: Started (was: Assigned)
ah. I think you have to not have a browser window open.
Project Member

Comment 10 by bugdroid1@chromium.org, May 10 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/eadedef7305278a22fca35db34b2831135ff5fb2

commit eadedef7305278a22fca35db34b2831135ff5fb2
Author: estade <estade@chromium.org>
Date: Wed May 10 22:20:09 2017

Fix activation issues with SystemTrayBubble.

1) Don't close on deactivation. The bubble is normally not
   activatable, but after pressing Tab it becomes activatable.
   It should behave the same in either case, so don't close
   on deactivation.
2) Explicitly close the info bubble instead of relying on
   activation changes which may or may not go through.

BUG= 716397 

Review-Url: https://codereview.chromium.org/2867933002
Cr-Commit-Position: refs/heads/master@{#470728}

[modify] https://crrev.com/eadedef7305278a22fca35db34b2831135ff5fb2/ash/system/network/network_state_list_detailed_view.cc
[modify] https://crrev.com/eadedef7305278a22fca35db34b2831135ff5fb2/ash/system/tray/system_tray.cc

Labels: -M-60 Merge-Request-59 M-59
This was caused by 0a0546417f0a60bb982 which is in m59 hence the crash affects m59.
Project Member

Comment 12 by sheriffbot@chromium.org, May 11 2017

Labels: -Merge-Request-59 Hotlist-Merge-Approved Merge-Approved-59
Your change meets the bar and is auto-approved for M59. Please go ahead and merge the CL to branch 3071 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), gkihumba@(ChromeOS), Abdul Syed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 13 by sheriffbot@chromium.org, May 15 2017

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 14 by bugdroid1@chromium.org, May 15 2017

Labels: -merge-approved-59 merge-merged-3071
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3ae3d987dd8fcad652c562bddc3ef66390eb65fc

commit 3ae3d987dd8fcad652c562bddc3ef66390eb65fc
Author: Evan Stade <estade@chromium.org>
Date: Mon May 15 16:44:36 2017

Fix activation issues with SystemTrayBubble.

1) Don't close on deactivation. The bubble is normally not
   activatable, but after pressing Tab it becomes activatable.
   It should behave the same in either case, so don't close
   on deactivation.
2) Explicitly close the info bubble instead of relying on
   activation changes which may or may not go through.

BUG= 716397 

Review-Url: https://codereview.chromium.org/2867933002
Cr-Original-Commit-Position: refs/heads/master@{#470728}
Review-Url: https://codereview.chromium.org/2876363004 .
Cr-Commit-Position: refs/branch-heads/3071@{#554}
Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}

[modify] https://crrev.com/3ae3d987dd8fcad652c562bddc3ef66390eb65fc/ash/system/network/network_state_list_detailed_view.cc
[modify] https://crrev.com/3ae3d987dd8fcad652c562bddc3ef66390eb65fc/ash/system/tray/system_tray.cc

Status: Fixed (was: Started)
Status: Verified (was: Fixed)

Sign in to add a comment