-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
[HVSXROAD] Crossroads of the Elements - crash report #625
Comments
This PR will fix the MBBSEmu log error you reported with the null exception while generating the crash report: #624 The other error looks interesting. We'll see if we can recreate it! |
We just crashed again, but this time LORD. It could be the same condition relating to channel exhaustion maybe? All 32 channels were full when it crashed.
|
I'm going to strike a new release that'll fix the unhandled exception while generating a crash report. Also -- do you find this error happens when you exceed your defined number of channels? |
Sounds good. Yes, it looks like MBBSEmu crashes a few times a day when the channels have been exhausted. |
Give v1.0-alpha-070124 a go, that should address both issues here. It'll prevent rlogin users from exhausting channels, and also fix the unhandled exception in the crash report. |
Ah, very good. Thank you. I'll get it up and running within the hour. Is the new fix just for rlogin? I'm only using Telnet at the moment. |
Telnet already has a block in place to prevent too many folks from logging in, so we should be good with this. |
I'm up and running with this new version. I'll let it soak for a few days. Thanks again for the quick work. |
Module Information
Describe the bug
MBBSEmu crashes and stops listening on TCP/23 when the logs appears as shown below.
To Reproduce
I don't know what the trigger is just yet.
Expected behavior
Do not crash. :)
Logs
MBBSEmu logs
Crash_HVSXROAD_20240620203059.txt
Software Information:
The text was updated successfully, but these errors were encountered: