Okay this is a dumb one, I think I fixed
Okay this is a dumb one, I think I fixed it. On top of the normal
message and close WS handlers, I also had a error one set up, which was supposed to remove the current connection from the list of connections, but wasn't necessarily closing the connection, such as if the client experienced an error, but not one that caused the socket to close. Somewhere, this was causing the socket to stay open or something. You can see a comparison in the screenshots
3 Replies
This still seems weird? Maybe I don't properly understand the situation, but if your DO wasn't receiving messages the DO should still hibernate. Unless you just mean your DO was trying to do work but wasn't able to because the WS client had gone away
I'm pretty sure its the latter
I'm away for a couple days but when back I can try and put together a repro and see if I can get it to happen again? I've had no issues since I changed some code
Sounds good, I'm actually gonna be out for a bit too, can circle back early Feb 🙂