I was using Netrunner, and I was logged into my Mystic BBS (a45) and I was using Stackfault's "Mystic Relay Chat."

I was in the chat, and I walked away from the computer for a while. I came back later, and my screen was filled with this message:

Runtime error 216 at $000000000040D9D0
$000000000040D9D0

Runtime....(this message over and over several times)

and also a message from Netrunner saying this:

Info
"Connection Terminated"
OK

I'm not sure what (if anything) I did to cause it to happen. I also can't say for sure if it's from Netrunner, Mystic itself, or the Mystic Relay Chat script.

This is the second time that it's happened. Any ideas?

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Runtime error 216 at $000000000040D9D0

I think this probably means the MRC client has a memory leak. What version of the client are you using? I just tried to reproduce the issue by logging in
and launching MRC, monitoring with 'htop'. Looks pretty stable over here, but there also isn't any chatter or anything.

I'll let it run for a bit and see what happens.

--- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
* Origin: monterey bbs (1:218/820)

I think this probably means the MRC client has a memory leak. What version the client are you using? I just tried to reproduce the issue by logging in

I'm using a customized version of the old Gryphon code. With that being said, maybe I messed something up.

I appreciate your input on this. "Memory Leak" is something I can read up on and hopefully figure out.

But if in case I fail to "fix the leak" maybe I can do a workaround with something like:

if errorlevel = 216 {code that will exit MRC & pass a message to the user telling them to log back in and try again}

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Re: Runtime_error_216
By: Aaron Thomas to All on Sat Apr 25 2020 00:00:19

Runtime error 216 at $000000000040D9D0
$000000000040D9D0

look here for the list of possible runtime errors that may be generated by programs written in freepascal...

https://www.freepascal.org/docs-html/user/userap4.html

in any case, there it nothing /you/ can do to fix this... it is a coding error... your only options are to downgrade or update to a version without this
defect...


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Runtime error 216 at $000000000040D9D0

I think this probably means the MRC client has a memory leak. What
version of the client are you using? I just tried to reproduce the issue by logging in and launching MRC, monitoring with 'htop'. Looks pretty stable over here, but there also isn't any chatter or anything.

I'll let it run for a bit and see what happens.

It could also mean they're running a Linux BBS and didn't recompile Python.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Sector 7 (1:129/215)

It could also mean they're running a Linux BBS and didn't recompile Python.

Interesting, I would never have guessed that. I couldn't reproduce this issue at all so maybe that's the problem...

--- Mystic BBS v1.12 A46 2020/04/13 (Linux/64)
* Origin: monterey bbs (1:218/820)

look here for the list of possible runtime errors that may be generated by programs written in freepascal...

Thanks for this info!

in any case, there it nothing /you/ can do to fix this... it is a coding

This chat script is open-sourced - the info you gave me gives me some avenues to inspect.

Thanks again!

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

It could also mean they're running a Linux BBS and didn't recompile Python.

Interesting, I would never have guessed that. I couldn't reproduce this issue at all so maybe that's the problem...

Yeah when Python isn't compiled in Shared mode so it can be embedded that is exactly the errors that pop up when trying to access Python's functions.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Sector 7 (1:129/215)

25 Apr 20 17:12, you wrote to g00r00:

It could also mean they're running a Linux BBS and didn't
recompile Python.

Interesting, I would never have guessed that. I couldn't reproduce
this issue at all so maybe that's the problem...

We did tests on Ubuntu and Debian last year. Recompilation often did not solve anything. Mystic's Python support on Linux was broken and only worked reliably on Ubuntu 18.04 IIRC.


* Origin: kakistocracy (2:280/464.47)