Article View: gnu.g++.lib.bug
Article #31Memory leak in libg++2.1 and 2.2
From: Alan Shepherd
Date: Mon, 20 Jul 1992 13:31
Date: Mon, 20 Jul 1992 13:31
17 lines
1080 bytes
1080 bytes
I think I have discovered a memory leak in libg++ in that the strstreambuf class allocated as part of istrstream's constructor is not deleted. istream::istream sets _flags to include dont_close and this means that _strbuf isn't deleted by ~istream and istrstream doesn't appear to have a destructor. Is this what you would expect ? I have a program which uses istrstreams and there is quite a large memory leak associated with its use. Alan Shepherd --------- Alan Shepherd, X-Tel Services Ltd., University Park, Nottingham NG7 2RD. Email: a.shepherd@xtel.co.uk, Phone: +44 (0) 602 412648 (Fax:790278) X.400: C=GB;ADMD= ;PRMD=X-Tel Services;O=X-Tel;S=Shepherd;G=Alan
Technical Details
Message-ID:
<16151.711631893@xtel.co.uk>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!xtel.co.uk!a.shepherdShow Full Headers
Complete Article Headers
Newsgroups: gnu.g++.lib.bug Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!xtel.co.uk!a.shepherd From: a.shepherd@xtel.co.uk (Alan Shepherd) Subject: Memory leak in libg++2.1 and 2.2 Message-ID: <16151.711631893@xtel.co.uk> Sender: gnulists@ai.mit.edu Organization: GNUs Not Usenet Distribution: gnu Date: Mon, 20 Jul 1992 13:31:33 GMT Approved: bug-lib-g++@prep.ai.mit.edu Lines: 19