New issue
Advanced search Search tips

Issue 898819 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 29
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Hangouts crashed bubble is not seen after ending it's process from task manager.

Reported by db...@etouch.net, Oct 25

Issue description

Chrome Version: 72.0.3590.0 (Official Build)Revision ec242826af28a2b3c3b47390ab6141cfe26fe9e7-refs/branch-heads/3590@{#1} (32/64 Bit).
Windows (7,8,8.1,10) and Linux(14.04 LTS). 

URL: https://chrome.google.com/webstore/detail/google-hangouts/nckgahadagoaajjgafhacjanaoiihapd?hl=en

What steps will reproduce the problem?
(1) Launch chrome, navigate to above url and click on 'ADD TO CHROME' button.
(2) Press Shift+Esc to open task manager and end the process of hangouts extension.
(3) Observe extension bubble.

Actual: Hangouts crashed bubble is not seen after ending process from task manager.

Expected: Hangouts crashed bubble should seen after ending process from task manager.

This is a regression issue, broken in 'M72', will soon update the other info:

Good Build:72.0.3585.0(Revision:601014)
Bad Build: 72.0.3586.0(Revision:601376)

Note: Issue is not seen on Mac(10.13.1, 10.13.6, 10.14.1) OS.
 
Actual_Bubble.mp4
631 KB View Download
Expected_Bubble.mp4
605 KB View Download
Labels: hasbisect
Owner: japhet@chromium.org
Status: Assigned (was: Unconfirmed)
Chromium bisect info:
  
https://chromium.googlesource.com/chromium/src/+log/3a5cf21878ea173391502d66113754ac1f669eb6..9bbc8c9b131838757133b308a282b74c77bb3da2?pretty=fuller&n=100

Suspecting: https://chromium.googlesource.com/chromium/src/+/6cd1de1d5ca6120479c95ac31a6a2f9b6e871fba

@japhet: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Note: Unable to provide bisect using Per-revision script as "RuntimeError: We don't have enough builds to bisect" error message is thrown hence provided suspect from chromium bisect.
				
Thank You.


Cc: japhet@chromium.org
Owner: tetsui@chromium.org
My CL is entirely code behind a flag, so definitely not it.

This is pretty far from blink, so my triage skills are limited, but my best guess from the regression range is https://chromium.googlesource.com/chromium/src/+/3a7d4419c4a183d1b8c1c90c83e538187b27d9a8

tetsui@, my apologies if my triage is way off.
Status: WontFix (was: Assigned)
Couldn't reproduce on ToT Linux (72.0.3596.0, 5afd3007276ae994a1c9fc5bb7da7363babb76e3)

The crash notification is properly shown.

Sign in to add a comment