Re: [Boost-bugs] [Boost C++ Libraries] #9151: memory leak in boost coroutines

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #9151: memory leak in boost coroutines
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-09-23 07:49:20

#9151: memory leak in boost coroutines
  Reporter: extproxy@… | Owner: olli
      Type: Bugs | Status: closed
 Milestone: To Be Determined | Component: coroutine
   Version: Boost 1.53.0 | Severity: Problem
Resolution: invalid | Keywords:
Changes (by olli):

 * status: new => closed
 * resolution: => invalid


 boost.coroutine creates an instance of a coroutine passed as argument to
 the coro-fn at the new stack stack.
 This coroutine instance will be destructed only if the stack is unwound.
 Unwinding is triggered only at destruction.
 Probably your profiling tool is not aware of this fact.
 You could take a look at example unwind.cpp which demonstrates that
 objects allocated on the coroutine stack will be deallocated (you could
 also add a destructor for push_coroutine which prints soem output if
 called - and you will see that this destructor will be called).

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:14 UTC