New issue
Advanced search Search tips

Issue 897681 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 3
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Service worker process gets stuck after clicking on Start button in chrome://serviceworker-internals page..

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

Issue description

Chrome Version: 72.0.3588.0 Revision 56533f367ba451d6545ab0045e8e11f288b36326-refs/branch-heads/3588@{#1}(32/64 bit)
OS: Windows (7, 8, 8.1, 10), Mac (10.13.1, 10.13.6, 10.14.1) and Linux (14.04 LTS)

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://serviceworker-internals/ page.
(2) Click on checkbox of open devtools window and click on Stop button then again click on Start button.
(3) Observe.

Actual: Service worker process gets stuck after clicking on Start button.

Expected: Service worker process should not stuck after clicking on Start button.

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

Good Build:66.0.3340.0(Revision: 534316)
Bad Build:66.0.3341.0(Revision: 534605)

Note: Issue is also seen on M70 Stable/Beta build #70.0.3538.67, M71 Dev build #71.0.3578.10
 
Actual_Process.mp4
569 KB View Download
expected_Process.mp4
494 KB View Download
Labels: hasbisect-per-revision
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
You are probably looking for a change made after 534602 (known good), but no later than 534603 (first known bad).
CHANGE-LOG URL:

https://chromium.googlesource.com/chromium/src/+log/3575ae4c91b80b24e56939e28f3c65cadbd47d8c..054856e6d33a1fd7b18b9c2154569ed07f666f5e	

Suspect: https://chromium.googlesource.com/chromium/src/+/054856e6d33a1fd7b18b9c2154569ed07f666f5e

@pfeldman: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thank You!
Status: WontFix (was: Assigned)
It might be that service-worker iternals are pointing to the wrong version of DevTools. In either case, serviceworker-internals is not a user-facing feature, so this is WontFix. We expect users to inspect workers from DevTools -> Application panel.

Sign in to add a comment