Closed
Bug 1425324
Opened 7 years ago
Closed 7 years ago
Websocket connections drops each 15 minutes
Categories
(Core :: Networking: WebSockets, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: antonkulaga, Unassigned, NeedInfo)
Details
Attachments
(1 file)
132.23 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171130143349
Steps to reproduce:
I regularly use notebooks to write code. They use websocket to maintain connection with the server ( https://github.com/spark-notebook/spark-notebook is a good example ). In Firefox Quantum when I opened a tab with spark notebook and then switched to another tab for 10-15 minutes Firefox drops websocket connection to the notebook, so I have to close and reopen it again. As I spend a lot of time analyzing data and coding this way I had to switch back to Chrome
Actual results:
In Firefox Quantum when I opened a tab with spark notebook and then switched to another tab for 10-15 minutes Firefox drops websocket connection to the notebook, so I have to close and reopen it again.
Expected results:
All websocket connections in the tabs should be opened, even if I spend an hour or two in another tab (it is quite common for me to have many Spark-notebooks opened and switching between them).
Component: Untriaged → Networking: WebSockets
Product: Firefox → Core
Comment 1•7 years ago
|
||
Hi Michal,
Would you take a look at this bug?
Thanks!
Flags: needinfo?(michal.novotny)
Reporter | ||
Comment 2•7 years ago
|
||
Any progress on this issue?
Comment 3•7 years ago
|
||
(In reply to antonkulaga from comment #2)
> Any progress on this issue?
Hi, I've tried to reproduce this with running Spark Notebook on my laptop, but I can't reproduce this.
Is there any public web site that can be used to reproduce this problem reliably?
Thanks.
Flags: needinfo?(antonkulaga)
Comment 4•7 years ago
|
||
I cannot reproduce it. We either need a link to a site where we can reproduce the problem or you could provide a log as described here: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging
The problem is that 10-15 minutes of logging can produce huge logs. Try to log following modules sync,timestamp,nsWebSocket:5,nsHttp:5,nsSocketTransport:5. To minimize log size use only as many tabs as really needed and try to keep firefox idle during those 10-15 minutes.
Flags: needinfo?(michal.novotny)
Reporter | ||
Comment 5•7 years ago
|
||
@:michal
Sorry, I was on the vocation. The bug is real, I need a week to deal with some urgent issues and then I will have some time to make logs for you.
Flags: needinfo?(antonkulaga)
![]() |
||
Comment 7•7 years ago
|
||
(In reply to Michal Novotny (:michal) from comment #4)
> I cannot reproduce it. We either need a link to a site where we can
> reproduce the problem or you could provide a log as described here:
> https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging
>
> The problem is that 10-15 minutes of logging can produce huge logs. Try to
> log following modules
> sync,timestamp,nsWebSocket:5,nsHttp:5,nsSocketTransport:5. To minimize log
> size use only as many tabs as really needed and try to keep firefox idle
> during those 10-15 minutes.
To keep the size of logs small, use MOZ_LOG and MOZ_LOG_FILE environment variables and add rotate:300 to the list of modules. If you want to use about:network#logging, it's fine too - then please zip (or xz) the log files before sharing.
Thanks.
![]() |
||
Updated•7 years ago
|
Whiteboard: ni?2018-01-25
![]() |
||
Updated•7 years ago
|
Whiteboard: ni?2018-01-25
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•