Someone else might be able to chime in with a more permanent solution. But for a temporary workaround, you could use something like this script[1] to clean up the modules manually after aborting jobs.
Cheers,
Jonathan
[1] https://sourceware.org/ml/systemtap/2008-q1/msg00051.html
----- Original Message -----
We use Systemtap in a continuous integration environment (Jenkins).
Sometimes, a job is aborted manually and it seems the Systemtap kernel
module is not unloaded then. As a result, several stap modules remain loaded
after aborting jobs the system runs out of memory.
Is there a way to prevent/fix this?
--CP
--
View this message in context:
http://sourceware-org.1504.n7.nabble.com/Systemtap-does-not-clean-up-properly-tp244731.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.