Hi ! Thank You for the response !
I wrote in my original message that the program is running on Solaris 8 (sparc). And I'm aware of Solaris quite special memory handling. And if I got It right, Solaris never frees memory to system but it still frees memory to same process that originally allocated it. So, the maximum allocated memory should then be == the largest block of memory allocated at given time. however, "my code" has ever allocated more than maybe 1 MB and even if it never allocates memory, it's still growing I also write a dummy-app to test the theory. I allocated and freed 100 MB in a loop. In Solaris the first loop took all 100MB and it got never released. But the 100MB remains constant over the next 5 - 6 loops. The exactly same code in Linux RH7.2 shows that memory is released between loops just like you say. so I don't think it's solaris-problem. Ofcource it can still be "my code" but I have not found the problem... So I took a chance and passed this question to list. Maybe somebody else have had the same problem?? Maybe libmysqlclient is not designed to be used in a daemon process?? It definitely is something wrong somewhere. 40 - 50 MB in a week is not normal, or what You think ?? I'will test hoard library asap, lets see what happens ! Thank You for Reading. =d0Mi= ---- Original Message ----- Date: 25-Apr-2002 18:30:57 +0200 From: Rick Flower <[EMAIL PROTECTED]> To: MySQL Mailing List <[EMAIL PROTECTED]> Subject: Re: Re: memory leaks in libmysqlclient. > dOMi writes: > > >However, after only a week the memory usage ocf this process > >has been grown to 40 - 50 MB so there's have to leakage somewhere. > > What you *may* be seeing is standard memory fragmentation that many > Unix' systems have with the standard allocator.. You don't mention > what platform you're on -- I'm assuming Unix. We've seen some of > our in-house software running for weeks at a time run into issues > such as this. While there were some minor leaks in our case, they > just didn't account for the large amounts of overhead/process size > over time. It really depends on what is being done behind the scenes > with allocations, etc.. If you're on a Linux system, the standard > allocator on that platform is better than most about keeping those > sorts of things from happening... If all else fails, you could > always plug something like Hoard in just for fun to see if the problem > goes away (it's free).. > > Hoard : http://www.cs.utexas.edu/users/emery/hoard/ > > -- Rick > > spamfilter : sql,query > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
