You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
```console
$ {name} version
# paste output here
```
Cloud provider
OS version
```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```
Install tools
The text was updated successfully, but these errors were encountered:
Bloomingg
changed the title
WEB端同一个浏览器开两个聊天窗口会导致26秒之后才能发送长链接请求
Opening two chat windows in the same browser on the WEB side will result in a long link request being sent after 26 seconds
Aug 7, 2024
What happened?
我们的WEB端是允许多端登录的,如果同一个浏览器开两个页面的话,26秒之后才能发送长链接请求。如果只保持一个窗口,页面一渲染就能发送长链接请求。初步判定是不是因为两个窗口都会走wasm里面的逻辑去处理本地数据,导致数据库存在资源竞争。并且先开的那个页面会报错:
![image](https://private-user-images.githubusercontent.com/62875064/321517393-76ae3205-69b0-45dc-a491-5cffb03d63be.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQzMjM1NjIsIm5iZiI6MTcyNDMyMzI2MiwicGF0aCI6Ii82Mjg3NTA2NC8zMjE1MTczOTMtNzZhZTMyMDUtNjliMC00NWRjLWE0OTEtNWNmZmIwM2Q2M2JlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODIyVDEwNDEwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTYxZjU0NzYxM2I0ZTdjYWJkYTYyOTVlMzVhNmEzY2U2M2RmZTdmZDVkY2I5MDE0NGQ0MmVjMjA2MWU0MzRiOTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.ahD4V1O93Xp9v-48vV1YIoiH1EGesyr5HbHlil_3t6s)
What did you expect to happen?
希望WEB端允许多端登录的情况下,不管同一个浏览器开多少个聊天窗口,都不影响长链接请求的发送时间。
How can we reproduce it (as minimally and precisely as possible)?
首先允许WEB端能够多端登录,然后先在浏览器里面打开一个聊天窗口,等到聊天链接成功之后,再打开一个新的聊天窗口,这个时候就能发现新开的聊天窗口要等很久才能链接成功(长链接请求接口才会发出)。
Anything else we need to know?
No response
version
Cloud provider
OS version
Install tools
The text was updated successfully, but these errors were encountered: