List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:June 23 2006 5:38am
Subject:Re: Query Object Memory Leak?
View as plain text  
Matt Dargavel wrote:
> To put my penny's worth in, trying it on Visual Studio Express with mysql++
> 2.0.7 shows the memory usage going up to about 65M as Bill describes (mine
> doesn't crash).  

Thanks for the data point.

> I'm not sure why the memory usage goes up so high, but it might have
> something to do with the fact that the runtime and O/S don't necessarily
> return any memory freed up to the general pool straight away (for efficiency
> reasons).

Yes, memory pool management does behave like you describe, but I don't 
see why the memory manager is requesting that many pages in the first 
place.  It should be able to create the query objects reusing the same 
memory block over and over again.
Thread
Query Object Memory Leak?Bill K21 Jun
  • Re: Query Object Memory Leak?Warren Young21 Jun
    • Re: Query Object Memory Leak?Bill K21 Jun
      • Re: Query Object Memory Leak?Warren Young21 Jun
        • Re: Query Object Memory Leak?Bill K21 Jun
          • Re: Query Object Memory Leak?Warren Young21 Jun
            • Re: Query Object Memory Leak?Bill K22 Jun
              • RE: Query Object Memory Leak?Matt Dargavel22 Jun
                • Re: Query Object Memory Leak?Bill K22 Jun
                  • Re: Query Object Memory Leak?Jim Langston22 Jun
                • Re: Query Object Memory Leak?Warren Young23 Jun
              • Re: Query Object Memory Leak?Warren Young23 Jun
                • Re: Query Object Memory Leak?Warren Young23 Jun
                  • RE: Query Object Memory Leak?Matt Dargavel23 Jun