From 408477a87aefbe3a972dfd66fcf907a09c4e7ac6 Mon Sep 17 00:00:00 2001 From: Moonchild Date: Wed, 16 Dec 2020 06:40:58 +0000 Subject: Revert "Issue #1695 - Add clamping to websocket polling timeouts." As of [da0c073a7] we no longer need this workaround because the issue is avoided with proper sleep/wake logic restored. This reverts commit 2fa993b5639e04c7e1d7403ecf9175a223ce50b4. --- modules/libpref/init/all.js | 5 ----- 1 file changed, 5 deletions(-) (limited to 'modules') diff --git a/modules/libpref/init/all.js b/modules/libpref/init/all.js index 8fcebed74..b6af98863 100644 --- a/modules/libpref/init/all.js +++ b/modules/libpref/init/all.js @@ -1660,11 +1660,6 @@ pref("network.websocket.timeout.open", 20); // close message pref("network.websocket.timeout.close", 20); -// Setting this to true will clamp the websocket timeout value to a minimum -// regardless if there are pending events on the thread. -// This is a workaround for runaway polling, see issue #1695 -pref("network.websocket.timeout.clamped", false); - // the number of seconds of idle read activity to sustain before sending a // ping probe. 0 to disable. pref("network.websocket.timeout.ping.request", 0); -- cgit v1.2.3