[BUG] background thread stops when session is destroyed, leading to weird errors

I’ve also seen this, the problem is likely that the dynamically created module for the session is cleaned up which probably clears out all globals even if the periodic function somehow persists. Will think about that in the context of this PR which is meant to allow global (i.e. non-session dependent) periodic callbacks.

1 Like