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

Issue 602988 link

Starred by 3 users
Status: Archived
Owner:
benwells@chromium.org
Closed: Jan 17
Cc:
█ animohan@chromium.org
xiy...@chromium.org
lazyboy@chromium.org
█ rpaquay@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

chrome.sockets onReceive is not raised on windows after inactivity

Reported by segaud.k...@gmail.com, Apr 13 2016 
Chrome Version       : 51.0.2699.0
OS Version: 8155.0.0

Chrome OS v51.0.2699.0: OK
Chrome on windows  v51.0.2700.0: FAIL

What steps will reproduce the problem?
1. create a chrome app with a socket
2. your app need to be able to send and receive message with the socket.
3. wait 20 seconds

an app who send a message when it start and listen to message.

launch the app on the first computer (the windows one) wait 20 seconds and launch the app on another computer.

What is the expected result?
Chrome API should raise the onReceive event


What happens instead of that?
Nothing :(


UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 8155.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2699.0 Safari/537.36

Comment 1 Deleted

Comment 2 by segaud.k...@gmail.com, Apr 13 2016 

an other example with just the background.
look at the background console
fail_example.zip
3.9 KB Download

Comment 3 by fbeaufort@chromium.org, Apr 13 2016

Cc: roc...@chromium.org
Components: Platform>Apps>API
Labels: -OS-Chrome OS-Windows
Ken can you have a look?

Comment 4 by fbeaufort@chromium.org, Apr 22 2016

Cc: animohan@chromium.org
Ani can you triage this please?

Comment 5 by animohan@chromium.org, Apr 22 2016 

I don't have the best context for this - Ken might have more context.

Comment 6 by fbeaufort@chromium.org, May 2 2016

Status: Available (was: Unconfirmed)
@rockot (gentle ping)

Comment 7 by roc...@chromium.org, May 2 2016

Cc: -roc...@chromium.org
Components: Platform>Extensions>API
Status: Untriaged (was: Available)
Putting in extensions triage queue.

Comment 8 by rdevlin....@chromium.org, May 13 2016

Cc: xiy...@chromium.org
Owner: rpaquay@chromium.org
Status: Assigned (was: Untriaged)
-> rpaquay for sockets.  xiyuan FYI.

Comment 9 by fbeaufort@chromium.org, Jun 11 2016

Cc: lazyboy@chromium.org
lazyboy@ is that something you can have a quick look?

Comment 10 by rpaquay@chromium.org, Jun 21 2016

Cc: rpaquay@chromium.org
Owner: ----
Status: Available (was: Assigned)
Marking available as I am not actively working on these issues anymore.
Project Member

Comment 11 by sheriffbot@chromium.org, Jun 22 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Comment 12 by lazyboy@chromium.org, Jun 23 2017

Owner: r...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to rkc for sockets.

Comment 13 by rdevlin....@chromium.org, Jun 23 2017

Components: -Platform>Extensions>API

Comment 14 by rkc@google.com, Jan 17

Owner: benwells@chromium.org
->Ben Wells for Apps

Comment 15 by benwells@chromium.org, Jan 17

Status: Archived (was: Assigned)
If I read this right, this works on Chrome OS but not on Windows. As Chrome apps are deprecated on Windows this has very low priority and won't realistically be fixed.
►

Sign in to add a comment