New issue
Advanced search Search tips

Issue 862833 link

Starred by 1 user
Status: WontFix
Owner:
hhli@chromium.org
Closed: Nov 14
Cc:
phanindra.mandapaka@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

It is difficult to tell service workers apart that are running in multiple user profiles

 
Chrome Version       : 67.0.3396.99
OS Version: OS X 10.13.6
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1.  Write code that users service workers from a path say /sw.js
2.  Create two profiles
3.  Run code in both profiles
4.  open chrome://inspect and view the list of service workers or shared workers
5.  observe there is no way to tell the multiple workers apart e.g. which profile is running which worker?

What is the expected result?

Some kind of indicator would be useful to include to indicate the source of the worker.  With ServiceWorkers you can have multiple listed even within the same profile making it very confusing when trying to debug.

What happens instead of that?

They all look identical

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
ServiceWorkerDebugging.png
124 KB View Download

Comment 1 by krajshree@chromium.org, Jul 12

Labels: Needs-Triage-M67

Comment 2 by dtapu...@chromium.org, Jul 12

Components: Platform>DevTools

Comment 3 by phanindra.mandapaka@chromium.org, Jul 13

Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback Triaged-ET
Thanks for filing the issue...

@Reporter : It would be really helpful if a sample URL is provided, so that we can investigate the issue further.

Thanks.!

Comment 4 by todd.fis...@calltrackingmetrics.com, Jul 13 

So this was something I triggered in my environment by creating two chrome profiles and working with either Service Workers or Shared Workers you can see this on any website.  The chrome://inspect shared worker or service worker does not indicate which chrome profile the worker belongs to...
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 13

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 6 by viswa.karala@chromium.org, Jul 25

Labels: Needs-Feedback
Tried testing the issue by creating two chrome profiles and accessing the same URL, observed only one instance got generated as shown in attached screenshot. 

@Reporter: Please find the attached screenshot for above mentioned and could you please confirm if this is a Feature request.

Thanks!

Comment 7 by l...@chromium.org, Aug 16

Owner: eostroukhov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 8 by dgozman@chromium.org, Oct 12

Owner: hhli@chromium.org

Comment 9 by dgozman@chromium.org, Nov 14

Status: WontFix (was: Assigned)
I think we now filter chrome://inspect to the profile it was opened in. Should not be an issue anymore.
►

Sign in to add a comment