Hi Gents,
I will give it a crack and have a wee' browse at it. I
have tried all sorts of hacks so far without going
into mysqlpp all to no avail.
Thanks,
Garyc
--- Matt Dargavel <matt@stripped> wrote:
>
> Hi Gary,
>
> This sounds like the leak Alex and myself
> looked at a while ago
> (see thread at http://lists.mysql.com/plusplus/5767
> ). Warren
> implemented a patch for it (see thread at
> http://lists.mysql.com/plusplus/6012 ). I'm not
> sure it's been released
> yet, but it's available from svn.
>
> Regards,
>
> Matt.
>
>
> gary clark wrote:
> > Hello,
> >
> > Not sure what is going on but I think I have found
> the
> > memory leak when running on windows using the
> purify
> > tool from IBM.
> >
> > I see Memory leak when calling the below code.
> > new(UINT)
> >
>
[f:\rtm\vctools\crt_bld\self_x86\crt\src\xiosbase.514]
> >
> >
>
std::ios_base::Init(void)[f:\rtm\vctools\crt_bld\self_x86\crt\src\xiobase
> >
> >
>
std::basic_ios<char,char_traits<char>::std>::init(basic_streambuf(char,char_traits<char>::std>::std
> > *,bool)
> >
> >
> > Ok this is why the leak occurred. I was using the
> > below statement.
> >
> > mysqlpp::Query query = con.query();
> >
> > The query is being created every time which inturn
> > creates an ostream which results in a leak. The
> query
> > object I now pass as a reference and then reset
> the
> > blighter which avoids the leak since only
> instantiated
> > once.
> >
> > Thanks,
> > Garyc
> >
> >
> >
>
> --
> MySQL++ Mailing List
> For list archives: http://lists.mysql.com/plusplus
> To unsubscribe:
>
http://lists.mysql.com/plusplus?unsub=1
>
>
