Zombie Threads

[fabian-jung]

If a cracen gets deleted, it tries to clean all of the allocated resources. However some threads are waiting on synchronus or asynchronus send or receive operations from graybat. Since there is no way to stop these threads either via graybat or via the std::thread interface, these may be stuck forever.

This should not be a problem, since the destructor is not called in continguous data processing (cracen instances are living over the whole programs lifespan) and even if some zombie threads are alive, they don't take much memory and nexto zero cpu time.

One problem might arise, if one zombie decides to wake up and acts on the released data. This would most likely lead to seg fault or undefined behaviour.