[BUG] websocket connection close in about 20-30s in Chrome

qiaoshangyougeren commented 1 month ago

OpenIM Server Version

3.5.2

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Docker Deployment

Bug Description and Steps to Reproduce

在chrome浏览器中，web应用连上open-im-server以后，一旦把浏览器最小化或切换到其他tab，就会出现这个账号隔20-30秒就下线然后重连成功，不断重复。如果页面一直在最前端显示，就不会反复断开重连。

open-im-server 里反复出现日志： msgGateway [msggateway/client.go:131] readMessage {"remoteAddr": "3.2.165.1:45582", "platform": "Web", "connID": "60ca83f08dc6d3b9d383f3ead3c6f587", "operationID": "1725609324430469397", "opUserID": "10", "messageType": -1, "error": "read tcp 10.201.10.6:10001->3.2.165.1:45582: i/o timeout"}

Screenshots Link

No response

Bloomingg commented 1 month ago

This is a problem with Chrome's mechanism. Inactive tabs may have their resources recycled.

qiaoshangyougeren commented 1 month ago

这个浏览器机制可以用什么方案规避吗？

我试过个别其他类型的im sdk好像不会有这个问题，有没有可以优化一下？

	@.***

@. | ---- Replied Message ---- | From | @.> | | Date | 09/10/2024 20:27 | | To | @.> | | Cc | @.>@.***> | | Subject | Re: [openimsdk/open-im-sdk-web-wasm] [BUG] websocket connection close in about 20-30s in Chrome (Issue #129) |

This is a problem with Chrome's mechanism. Inactive tabs may have their resources recycled.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

openimsdk / open-im-sdk-web-wasm