Algorithm destructor not invoked in multithreading applications

I modified the algorithm destructor test to use AlgResourcePool, HiveSlimEventLoopMgr and AvalancheSchedulerSvc, and the destructor of the algorithms is not called.

/cc @wlampl

changed milestone to %v35r0

changed the description

mentioned in merge request !1149 (merged)

changed title from Algorithm destructor not invoked in multithrading applications to Algorithm destructor not invoked in multithreading applications

It turned out that AlgResourcePool keeps 3 SmartIF instances of the algorithms, but delegates management of the algorithms states to the AlgorithmManager.

AlgorithmManager implicitly deletes managed the algorithms during finalize, but this cannot happen because of the refcount in AlgResourcePool.

Adding a finalize to AlgResourcePool so that we clean up the ref count, algorithms' destructors are called at that point.

In principle they should be called when AlgResourcePool is destroyed, but it looks like the destructor is never invoked, most probably because, again, of ref count problems.

Now I'd like to understand why AlgResourcePool is not invoked, and when we should destroy algorithms (is it OK to do it at AlgResourcePool finalization, or should we do it at destruction?)

changed milestone to %v35r1

closed with merge request !1149 (merged)

mentioned in commit 043fdd70