Socket IO disconnect leads to no IPC
See original GitHub issue- Version: 8.31.2
- .NET Core version 3.1
- Target: Windows 10
When running my Electron.NET application for a while, sometimes a few minutes, sometimes up to half an hour, I get the following messages printed in my console:
Got disconnect!
ASP.NET Core Application connected... global.electronsocket C2zRUaIlrhDjLVRMAAAE 2020-06-11T17:49:54.749Z
stdout: BridgeConnector connected!
After which no IPC can be processed, leaving my app in a frozen state in which just the JS works.
This seems to occur at random times, with no actual reason leading to the cause (atleast I can’t figure out what the cause is).
Can somebody help me out with this?
Thanks in advance!
Issue Analytics
- State:
- Created 3 years ago
- Comments:20 (6 by maintainers)
Top Results From Across the Web
The Socket instance (server-side)
... there is no message queue stored for a given ID on the server (i.e. if the client is disconnected, the messages sent...
Read more >Socket.io client disconnects due to ping timeout / transport ...
I realised that my web page was eating up RAM, which was causing the client socket to hang and not send any data...
Read more >Create a Secure Chat Application with Socket.IO and React
The disconnect and connection_error are predefined events that are triggered when the socket disconnects, or when an error happens during the ...
Read more >ZeroMQ: Messaging for Many Applications
OMQ sockets do their I/O in abackground thread. ... The zmq_msg_send () method does not actually send the message to the socket connection(s)....
Read more >Net | Node.js v20.5.1 Documentation
The node:net module supports IPC with named pipes on Windows, ... Socket , the 'close' event will not be emitted directly following this...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No, I still plan on looking into the menu issue. It’s on top of my free time list as I expect it will impact my own project. However the general socket issues are fixed around Ipc connectivity with the browser windows. That’s what my fix targeted as mentioned in the other ticket.
At the moment I’m heads down getting the first release done for my project as it’s due to be delivered by next week. I hope to get to the menu issue prior to next week but deadlines are deadlines.
🎉🚀 New Electron.NET version 23.6.1 released 🚀🎉
With native Electron 23 and .NET 6 support. Your problem should be fixed here. If you continue to have the problem, please let us know. Please note the correct updating of your API & CLI. Info in the README. Have fun!