-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PT10 - Websockets get disconnected #1419
Comments
The peculiar part in the log starts at 13:17:11:
Before that point, everything appears to have been working as expected. Then at 13:17:11 the first sign of a disconnect happens (websocket 3 is the one between main and the renderer). But the teardown after the websocket closed didn't finish until 17 minutes later, at 13:34:09. That is very odd and indicates the main process (which is where the "Method removed" messages originate) was so bogged down it couldn't quickly finish running through a this.rpcMethodDetailsByMethodName.forEach(({ handler }, methodName) => {
if (handler !== this) return;
logger.info(`Method '${methodName}' removed since websocket ${this.name} closed`);
this.rpcMethodDetailsByMethodName.delete(methodName);
}); My best guess at this point is that something bad was happening inside the main process which caused the websocket to close. What that could be is still a mystery. Notice that the |
Describe the bug
I noticed this when working with PT10, the WebSockets get disconnected silently. The application does not work as it should and the user is not aware of it. The application needs to be restarted to work normal
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
main_websocket_disconnected.log
The text was updated successfully, but these errors were encountered: