-
Notifications
You must be signed in to change notification settings - Fork 7
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
More information on the crash. #1
Comments
I just played a bit with it and didn't manage to trigger a crash, so I really don't know. But I remember having such a problem and felt I should warn about it. The main problem, however, not connected to crashing, is that every new client is assigned a new thread which might cause issues when a really large group of clients were to connect. But I made this as a personal learning project, not a professional solution in any way. If you have any suggestions or will find any bugs, feel free to share them and/or contribute 😃 |
I left the server running for some time (and forgot about it, to be honest) and after that, I visited
Quick googling suggests I messed up something with threads. I might look into this in free time. |
I suspected it might be threads at first. This is for windows and the first thing that came into my mind was why aren't windows threads being used. Yes I want to contribute. I'll try fixing this and also try making a version with Windows threads. |
I don't understand, why would you use Windows threads, if C++ offers an abstraction over them. Right now, porting to BSD socket API is trivial, after this change it won't be. |
As you've stated, It sometimes crashes. Can I see why and where? What exception causes it to crash? And how does it crash?
The text was updated successfully, but these errors were encountered: