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
Destruction happens bottom-up, meaning that once the ~monitor method is executing, the subclass is not existent anymore and the on_stop method will dispatch to the no-op one.
This is a blocking issue for who is using the C binding as destroying a monitor is the only way to stop it.
I suggest that every subclass of monitor should call stop() explicitly.
The text was updated successfully, but these errors were encountered:
The destructor calling stop() was meant as a safety net: each monitor should be stopped gracefully with stop(). The C binding is missing a stop() function and that's what I think we should add for starters.
Destruction happens bottom-up, meaning that once the
~monitor
method is executing, the subclass is not existent anymore and theon_stop
method will dispatch to the no-op one.This is a blocking issue for who is using the C binding as destroying a monitor is the only way to stop it.
I suggest that every subclass of
monitor
should callstop()
explicitly.The text was updated successfully, but these errors were encountered: