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
..
include	core: do not destroy in object pool's apply scope	2015-09-30 12:20:40 +02:00
context_area.cc	base: introduce caching attributes (fix #1184)	2014-06-26 10:57:26 +02:00
cpu_session_extension.cc	base: redesign object pool using lambda interface	2015-09-09 15:14:28 +02:00
cpu_session_support.cc	CPU session: apply quota via relative weightings	2015-05-06 10:55:16 +02:00
io_mem_session_component.cc	Move repositories to 'repos/' subdirectory	2014-05-14 16:08:00 +02:00
pd_session_component.cc	base: redesign object pool using lambda interface	2015-09-09 15:14:28 +02:00
platform_thread.cc	Move repositories to 'repos/' subdirectory	2014-05-14 16:08:00 +02:00
platform.cc	safeguard the synchronized allocator template	2015-09-30 12:20:39 +02:00
ram_session_support.cc	Move repositories to 'repos/' subdirectory	2014-05-14 16:08:00 +02:00
rom_session_component.cc	base: introduce caching attributes (fix #1184)	2014-06-26 10:57:26 +02:00
target.mk	Remove always_hybrid spec	2015-09-09 15:14:27 +02:00
thread_linux.cc	thread API & CPU session: accounting of CPU quota	2014-11-28 12:02:37 +01:00