Stefan Kalkowski b585583ec7 core: do not destroy in object pool's apply scope ... Destroying an object within the scope of a lambda/functor executed in the object pool's apply function leads potentially to memory corruption. Within the scope the corresponding object is locked and unlocked when leaving the scope. Therefore, it is illegal to free the object's memory meanwhile. This commit eliminates several places in core that destroyed wrongly in the object pool's scope. Fix #1713		2015-09-30 12:20:40 +02:00
..
base	base: redesign object pool using lambda interface	2015-09-09 15:14:28 +02:00
core	core: do not destroy in object pool's apply scope	2015-09-30 12:20:40 +02:00
lib/startup	Introduce 'spec' subdirectories to outline aspects	2015-09-16 13:58:50 +02:00
test	run/cpu_quota: raise measurement precision further	2015-07-21 09:30:12 +02:00