New issue
Advanced search Search tips

Issue 919883 link

Starred by 1 user
Status: Duplicate
Merged: issue 863846
Owner: ----
Closed: Jan 11
Cc:
vamshi.kommuri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Network tab empty when debugging SharedWorker

Reported by dunba...@gmail.com, Jan 8 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Steps to reproduce the problem:
1. Create a SharedWorker that makes HTTP/websocket requests
2. Find the SharedWorker in chrome://inspect
3. Open the debugger
4. Click the Network tab

What is the expected behavior?
Network traffic should be displayed in the network tab of the devtools.

What went wrong?
The network tab is blank. Nothing is displayed.

Did this work before? N/A 

Chrome version: 71.0.3578.98  Channel: stable
OS Version: OS X 10.14.2
Flash Version:

Comment 1 by mef@chromium.org, Jan 8

Components: Internals>Network
I'm not sure there is something that networking team can help with, so adding the component just in case.

Comment 2 by susan.boorgula@chromium.org, Jan 9

Labels: Needs-Triage-M71

Comment 3 by vamshi.kommuri@chromium.org, Jan 9

Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

@Reporter: Could you please share a sample test file which helps us us to triage this further in a better way. Any further inputs from your end may be helpful.

Comment 4 by dunba...@gmail.com, Jan 10 

Sure thing! The attached file reproduces the error. You can see successful network requests in the console but no content in the network tab.
index.html
440 bytes View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 10

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 dunba...@gmail.com, Jan 10 

I did some digging into the source and found that this is already fixed by the following commit in master:

https://chromium.googlesource.com/chromium/src/+/b1da81df435473b66953179d3fc0e65a1bb57366

Can you tell me how to find out when that commit will make its way into stable Chrome?

Also, I suppose we could merge this bug with the one reported there:

https://bugs.chromium.org/p/chromium/issues/detail?id=863846

Comment 7 by vamshi.kommuri@chromium.org, Jan 11

Mergedinto: 863846
Status: Duplicate (was: Unconfirmed)
@dunbarb2: Thanks for your inputs....!
As this seems to be similar to that of  Issue 863846 , hence merging into it and marking it as Duplicate.

Thanks!
►

Sign in to add a comment