Spud,
Looks like there is a fairly signifiant issue with the Autelis plugin version 3.0.0.22 on Linux. I have been fighting constant out of memory issue occurring in the HSConsole.exe application and have been turning off all my plugins and turning them on one by one. When I enable the current Autelis plugin my memory usage goes from about 9% to 20% pretty quickly and if I leave it running the system crashes and HSSentry restarts everything. This happens 2-6 times a day. The plugin also seems to go to very high CPU and takes quite a while to stop. Now ideally nothing a plugin can do should effect HSConsole like this (since they are separate processes), but perchance are you doing any work in any of the below calls (HSConsole loads the modules into its memory to call those, then unloads the app domain then launches the actual HSPI_plugin. So threads started (etc) in any of these calls wind up running inside of HSConsole on the first load, and again in your plugin on the real load).
Name
AccessLevel
Capabilities
comport
supportsMultipleInstances
supportsMultipleInstancesSingleEXE
Rich is aware, I will ask him to reach out and see if the three of us can figure out why this is occurring and what we can do to ensure HSConsole at a minimum can't be crashed by a plugin.
Help
Best
Bill
Looks like there is a fairly signifiant issue with the Autelis plugin version 3.0.0.22 on Linux. I have been fighting constant out of memory issue occurring in the HSConsole.exe application and have been turning off all my plugins and turning them on one by one. When I enable the current Autelis plugin my memory usage goes from about 9% to 20% pretty quickly and if I leave it running the system crashes and HSSentry restarts everything. This happens 2-6 times a day. The plugin also seems to go to very high CPU and takes quite a while to stop. Now ideally nothing a plugin can do should effect HSConsole like this (since they are separate processes), but perchance are you doing any work in any of the below calls (HSConsole loads the modules into its memory to call those, then unloads the app domain then launches the actual HSPI_plugin. So threads started (etc) in any of these calls wind up running inside of HSConsole on the first load, and again in your plugin on the real load).
Name
AccessLevel
Capabilities
comport
supportsMultipleInstances
supportsMultipleInstancesSingleEXE
Rich is aware, I will ask him to reach out and see if the three of us can figure out why this is occurring and what we can do to ensure HSConsole at a minimum can't be crashed by a plugin.
Help
Best
Bill
Comment