You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this specific limitation apply to the module
"Multi-CPU is done with OS threads, not processes. A lane is a Lua full userdata, therefore it will exist only as long as the Lua state that created it still exists. Therefore, a lane won't continue execution after the main program's termination."
Specifically the part about using OS threads not processes. aswell if this limitation does apply, is there already a means of removing old lanes no longer being used when say a server shuts down? For example lets say 4 lanes were made and then the normal gmod lua state. when srcds is shut down, do these lanes get cleaned up with it or no? and if not is it possible to implement a means of cleaning them up?
The text was updated successfully, but these errors were encountered:
When a process is terminated, any resources associated to it get freed. This includes OS threads and any Lua states. Nothing gets left behind (unless there's bugs in the OS but that's another thing). However, you should make sure to finish any work on any Lane to prevent losing data but that's up to you.
Does this specific limitation apply to the module
"Multi-CPU is done with OS threads, not processes. A lane is a Lua full userdata, therefore it will exist only as long as the Lua state that created it still exists. Therefore, a lane won't continue execution after the main program's termination."
Specifically the part about using OS threads not processes. aswell if this limitation does apply, is there already a means of removing old lanes no longer being used when say a server shuts down? For example lets say 4 lanes were made and then the normal gmod lua state. when srcds is shut down, do these lanes get cleaned up with it or no? and if not is it possible to implement a means of cleaning them up?
The text was updated successfully, but these errors were encountered: