Closed
Bug 1386317
Opened 8 years ago
Closed 7 years ago
Tabs are expired with active WebSocket connection
Categories
(Firefox for Android Graveyard :: Web Apps (PWAs), defect)
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: juhamatk, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170628075643
Steps to reproduce:
I opened one tab with active WebSocket connection on TCP and several other tabs.
Actual results:
When I used other tabs and kept the WebSocket connection on the background, it was expired there, i.e. when the WebSocket tab was eventually selected it started from beginning (re-established websocket connection etc, instead of restoring just the view to original connection).
Happens easily on Andoird Firefox, same thing does not happen on Windows Firefox in similar way, at least as easily.
Expected results:
In case of active websocket connection, the tab should not expire. This would be similar to a case where an audio file is played on the tab: these tabs do not expire.
Comment 1•8 years ago
|
||
We'd want to add some state in the tab object to track if there are any websocket connections open, and then update the check at [1] to also skip zombification if websockets are open.
[1] http://searchfox.org/mozilla-central/rev/bbc1c59e460a27b20929b56489e2e55438de81fa/mobile/android/chrome/content/browser.js#7007
Comment 2•8 years ago
|
||
Hi! Any chance ti getbthis fixed soon? Anything I can help with?
I tested this on Firefox 55.0.3 for Windows and happens there too, but not as aggressively. A fix would be nice. Workaround is to loop a silent audio file constantly. It will be seen on Firefox for Android as a separate streaming icon in the headbar so workaround is not transparent really.
Workaround in detail:
//global scope
myAudio = new Audio('silence.ogg');
myAudio.loop = true;
myAudio.play();
Component: General → Web Apps
Comment 5•7 years ago
|
||
Closing per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195
Contact :susheel if you think this bug should be re-opened
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•