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

Issue 818074 link

Starred by 1 user
Status: Duplicate
Merged: issue 811403
Owner:
█ eostroukhov@chromium.org
Last visit > 30 days ago
Closed: Mar 2018
Cc:
vamshi.kommuri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Empty websocket frames

Reported by ahshum...@gmail.com, Mar 2 2018 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:
1. Go to http://www.websocket.org/echo.html
2. open developer tool > network tab > ws
3. Click "connect" and "send" in the web page. The frames is still empty

What is the expected behavior?
Packet should be logged in the frames tab.

What went wrong?
Websocket packet is not logged.

Did this work before? Yes Stable 63

Chrome version: 64.0.3282.186  Channel: stable
OS Version: Debian 9.2
Flash Version:

Comment 1 by ajha@chromium.org, Mar 2 2018

Labels: Needs-Bisect Needs-Triage-M64

Comment 2 by vamshi.kommuri@chromium.org, Mar 2 2018

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

Unable to reproduce the issue on reported chrome version 64.0.3282.186 using Ubuntu 14.04 with the below mentioned steps.
1. Launched Chrome
2. Navigated to http://www.websocket.org/echo.html
3. Opened DevTools -> Network tb -> WS
4. Clicked on "connect" and "send"
We observed Websocket packets are logged. Attaching the screen cast of the same.

@Reporter: Could you please have a look at the screen cast and let us know if we have missed anything in the process of reproducing the issue. Any further inputs from your end may help us.
818074.mp4
2.3 MB View Download

Comment 3 by ahshum...@gmail.com, Mar 2 2018 

Sorry for unclear step to reproduce.

After clicked "send", the "frames" under WS session is empty. Attaching the screen cast for a clearer steps to reproduce.
Mar 2, 2018 5_40 PM.webm
4.6 MB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 2 2018

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 5 by alph@chromium.org, Mar 2 2018

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

Comment 6 by eostroukhov@chromium.org, Mar 2 2018

Labels: -Needs-Bisect -Needs-Triage-M64 Needs-Feedback
I am unable to reproduce this. Please try running Chrome with a new profile and no enabled extensions.

Comment 7 by ahshum...@gmail.com, Mar 2 2018 

I found that when env variable "TZ" is not set, the WS frames is empty and 

(new Date).toLocaleDateString()
returns
Uncaught RangeError: Unsupported time zone specified undefined
    at new DateTimeFormat (native)
    at Date.toLocaleDateString (native)
    at <anonymous>:1:12

which was not happened in Chrome 63.

Comment 8 by eostroukhov@chromium.org, Mar 2 2018

Mergedinto: 811403
Status: Duplicate (was: Assigned)
Interesting. Looks like this is a dupe of 811403 then.
►

Sign in to add a comment