Socket closes when tab is in background – is ping/pong paused?

[yasmanets]

Hi! I'm experiencing an issue where the WebSocket connection gets closed when the browser tab is left in the background for a while.

I’m using the following config:

const { sendMessage } = useWebSocket(socketUrl,
	{
		heartbeat: {
			message: encodeMsg({ action: 'ping' }),
			returnMessage: `pong`,
			timeout: 3000,
			interval: 500
		},
		shouldReconnect: () => {
			return true;
		},
		reconnectInterval: 300,
		reconnectAttempts: 10
	},
);

What happens:

When I leave the tab inactive (e.g., switch to another tab or minimize the browser), after some time the WebSocket connection closes.
This seems to happen because the ping/pong messages stop being sent or received.
When I return to the tab, a new socket is created, triggering a reconnection.

My question:

Does react-use-websocket pause activity (like sending/receiving ping/pong or timers) when the tab is in the background or suspended by the browser?

If so, is there a recommended way to keep the connection alive or resume it properly once the tab becomes active again?

Thanks in advance!

[yasmanets]

I have found the answer here:

https://github.com/robtaussig/react-use-websocket/blob/master/src/lib/heartbeat.ts#L29-L32

[happier2]

I have found the answer here:

https://github.com/robtaussig/react-use-websocket/blob/master/src/lib/heartbeat.ts#L29-L32

Hi Yasmanets, We just have this same issue. Could you please tell us that how you solved this problem?

[happier2]

I have found the answer here:
https://github.com/robtaussig/react-use-websocket/blob/master/src/lib/heartbeat.ts#L29-L32

Hi Yasmanets, We just have this same issue. Could you please tell us that how you solved this problem?

I have found the answer. From the chrome 88 release, setInterval throttling will be done more intensively, at 1 minute.
Overcoming browser throttling of setInterval executions | Medium