Is this the only place this will cause trouble? A quick search shows basic_stringstream being in use in lexical case and serialization. - and in my own code :-(( Is there a problem here too? Paul PS I find the 'fixed' from Microsoft not really good enough - it involves rebuilding a dll. (Considering the amount of trouble it is likely to cause). Why can't they provide a new ready-built dll? I may get round to asking for this. -- Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB Phone and SMS text +44 1539 561830, Mobile and SMS text +44 7714 330204 mailto: pbristow@hetp.u-net.com http://www.hetp.u-net.com/index.html http://www.hetp.u-net.com/Paul%20A%20Bristow%20info.html | -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of Jeff Garland | Sent: 18 February 2006 21:13 | To: boost@lists.boost.org | Subject: Re: [boost] [date_time] [MSVC8] Memory leak in | operator<<(ptime) | | On Sat, 18 Feb 2006 14:12:16 -0500, Sean Huang wrote | | > Jeff, | > | > Thanks! I've tried the new version and the memory leak stopped | > I also did a search in data_time | > and found there are other places where basic_stringstream could be | > replaced with basic_ostringstream.