Currently, if you launch any mod from STANDALONE build of AutoBleem there is an issue where the Autobleem-GUI is left running and fighting the launched app for framebuffer access and resource.
This is killing performance.
In the packaged build, I have included a VERY crude workaround which ensures that the AB thread is killed fully when a mod is selected, however it also uses PE launching logic so it's not applicable to standlone.
The recommendation is to refactor alot of the shell launching of the app and consolidate within 1 single shell which takes command line arguments. Also if you source the bash when starting instead of launching it. The sourced bash doesn't generate it's own PID.
Because of this you are unable to kill -s STOP and kill -s CONT the AB launcher wrapper and kill the autobleem-gui process inbetween.
The ideal situation would involve:
Single entry bash with command line argument parsing
When mods are launched. The wrapper is suspended and the gui killed with fire
When the mod is finished, continue the wrapper which should start up gui again.
For the above to happen you would need to record last screen pos and restore that within the SDL application.
Currently, if you launch any
mod
from STANDALONE build of AutoBleem there is an issue where the Autobleem-GUI is left running and fighting the launched app for framebuffer access and resource.This is killing performance.
In the packaged build, I have included a VERY crude workaround which ensures that the AB thread is killed fully when a mod is selected, however it also uses PE launching logic so it's not applicable to standlone.
The recommendation is to refactor alot of the shell launching of the app and consolidate within 1 single shell which takes command line arguments. Also if you source the bash when starting instead of launching it. The sourced bash doesn't generate it's own PID.
Because of this you are unable to kill -s STOP and kill -s CONT the AB launcher wrapper and kill the autobleem-gui process inbetween.
The ideal situation would involve: