Boost C++ Libraries: Ticket #8526: coroutine memory leak

status changed; resolution set

olli — Tue, 30 Apr 2013 08:52:39 GMT

status new → closed
resolution → invalid

the caller is allocated on the stack of the calling coroutine - the destructor will not be called but the stack (memory) is released or reused after the calling coroutine is destroyed - so it is not a memory leak.

status changed; resolution deleted

olli — Wed, 01 May 2013 08:11:23 GMT

status closed → reopened
resolution invalid

status changed; resolution set

olli — Wed, 01 May 2013 09:27:29 GMT

status reopened → closed
resolution → fixed

rivercheng@… — Fri, 31 May 2013 04:31:38 GMT

Hi, Oliver Could you please explain how this bug is fixed? It exists in 1.53 release and I want to know whether I can make a small change to existing codes to fix this problem instead of waiting for another release. Thanks a lot.

olli — Fri, 31 May 2013 06:18:09 GMT

Replying to rivercheng@…:

Hi, Oliver Could you please explain how this bug is fixed? It exists in 1.53 release and I want to know whether I can make a small change to existing codes to fix this problem instead of waiting for another release. Thanks a lot.

void run() {

... {

Caller c( this->caller_, false, this->preserve_fpu(), alloc_); fn_( c); ...

} ...

}

If coroutine is unwinded fn_() throw unwind-excpetion and Caller ist automatically destructed.