New issue
Advanced search Search tips

Issue 602994 link

Starred by 3 users

Issue metadata

Status: Archived
Owner:
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

EventSource 'onopen' event is inconsistent in state

Reported by realgran...@gmail.com, Apr 13 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 7834.70.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Platform: 7834.70.0 (Official Build) stable-channel falco

Steps to reproduce the problem:
1. create many s=EventSource(); s.onopen=function(){s.close()};
2. in my case these were created by ~20 iframes
3. some connections reach the server (get opened) and some not

What is the expected behavior?
Either no connection is opened in this case and aborted, or all connections are opened and then closed

What went wrong?
Some of the connections are closed before they are opened, and some are behaving as expected - the request is first seen at the server side, then onopen fires and the connection get closed.

Did this work before? N/A 

Chrome version: 49.0.2623.112  Channel: stable
OS Version: 7834.70.0
Flash Version: Shockwave Flash 21.0 r0

in Firefox, the connection is first seen on server, then onopen() is fired

This may happen only on slow hardware though
 
Components: -Blink Blink>PushAPI
Components: -Blink>PushAPI Blink>Messaging
Not sure exactly where this lives, but moving it further in what is probably the right direction in the hopes that it finds a home

Comment 3 by tkent@chromium.org, May 11 2016

Components: -Blink>Messaging Blink>Network
Labels: Needs-Feedback
Owner: yhirano@chromium.org
Sorry for the late response. Could you provide a net-internals log?

https://dev.chromium.org/for-testers/providing-network-details
Project Member

Comment 5 by sheriffbot@chromium.org, Mar 22 2017

Status: Archived (was: Unconfirmed)
No feedback was received in the last 30 days from reporter "realgrandrew@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment