Boost C++ Libraries: Ticket #7156: interprocess buffer streams leak memory on construction

attachment set

Fri, 20 Jul 2012 19:15:22 GMT

attachment → bufferstream_leak.cpp

Very crude program which demonstrates the leak. Bufferstream types are constructed in a loop along with an int on the heap. The address of the integer advances with each iteration.

attachment set

Fri, 20 Jul 2012 19:18:04 GMT

attachment → bufferstream.hpp.patch

Patch which seems to fix the leak.

Tue, 16 Oct 2012 23:50:05 GMT

The same leak appears in vectorstream family of classes, too. Tested with Boost 1.51.

anonymous — Wed, 21 Aug 2013 06:30:10 GMT

We are also facing this issue. please fix this in the official boost release.

Ion Gaztañaga — Tue, 03 Sep 2013 21:58:35 GMT

This is a known problem of the MSVC STL implementation. However, basic_ios::init call should be called only once, as the standard does not give any guarantee to allow calling it twice (MSVC STL leaks in this case). As pointed in http://accu.org/index.php/journals/264 we need to take of a potentially throwing custom streambuf so that basic_ios is not destroyed without being initialized. This is not a problem for bufferstream (has nothrow constructors) but it could affect vectorstream. In this second case a null streambuf will be passed to initialize basic_[i/o]stream, which will call basic_ios::init. After that, the streambuf will be replaced with vectorstream.

status changed; resolution set

Ion Gaztañaga — Tue, 03 Sep 2013 22:03:11 GMT

status new → closed
resolution → fixed

(In [85555]) Fixes #7156