This is the mail archive of the
mailing list for the libstdc++ project.
Re: Memory leak in ios.cc:326
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: weigand at immd1 dot informatik dot uni-erlangen dot de
- Date: Thu, 27 Mar 2003 15:14:22 -0600 (CST)
- Subject: Re: Memory leak in ios.cc:326
- Organization: Networks and Infrastructure Lab (IL02/2240), Motorola Labs
>> While testing libcwd with g++-3.3, I run into a
>> possible memory leak at ios.cc:326:
> This may or may not be related, but I'm also seeing what
> appears to be a memory leak with the 3.3 libstdc++:
> the thread3.cc test case times out, and while looking at
> the process while it is running, it's RSS continually
> grows until the machine start swapping and everything
> gets slow (which is why the case times out eventually).
> Seeing as that test case basically only does this
> (in two threads in parallel):
> for (int i = 0; i < max_loop_count; i++)
> std::ostringstream oss;
> I don't really see why it should need hundreds of
> megabytes of memory ...
I have my hands full at the moment, but I wanted to ACK this message.
At the time the 6 threaded C++ tests were installed, I personally
checked all of them to ensure that there were zero systemic memory
leaks on (at least) i386-*-freebsd*. If you are seeing a leak on a
machine, then it is either a general regression or per-port
regression. Given the description, I'd call it rather major. I've
been seeing time outs on some of the threaded tests on my local
machine but I thought it correlated to the switch to generic atomics
for "pure" i386.
If you file a PR and assign it to me, then it will get looked at but
perhaps not before 3.3 is released.