List:MySQL++« Previous MessageNext Message »
From:Warren Young Date:June 23 2006 5:30am
Subject:Re: Query Object Memory Leak?
View as plain text  
Bill K wrote:
> Crashes, eh? It doesn't crash for me.

Well, that's weird enough to deepen my resistance to the idea that the 
problem is in MySQL++.  The version of MySQL++ is one of the few things 
that we absolutely know are common between our two systems.

I'd be curious to know if:

1. It behaves exactly the same when you use VC++ 2003 vs. 2005.  Any 
difference at all?

2. Can you try MySQL++ 2.0.0?  That would help to pin down the issue of 
whether it's the Query base class change, and not something else.

	http://tangentsoft.net/mysql++/releases/mysql++-2.0.0.tar.gz

3. What version of MySQL are you building against?  The problem could be 
down in the C API.  I'm using 4.1.14 on my Windows machine.  (No 
particular reason I'm on this older version...just no good reason to 
upgrade yet.)

> Adding an "if( !(i%1000) ){ 
> std::cout << i << endl;  }" in the loop, I can see it fly through and 
> finish all million loops, using over 80MB of memory at the end, 
> according to Windows Task Manager.

I did something very similar, but mod 10,000 instead, and only got a few 
dots before it dereferenced a null pointer.
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