radada wrote:
Hi and thanks four your answer.
The ElementXML is a class from scratch that only contains a pointer to a
DOMNode element. It's only here to redefine some methods to access the
Elements inside a DOMNode.
Didn't knew about valgring. I compile on AIX so I'll give it a try.
Valgrind only runs on x86 hardware, so you cannot use it.
The weirdest thing happened : my program is a short of demon. It runs
"forever" and treats the files I put in a folder (to sum up). When I give it
3000 files, I get a core dump with the memory growing up to 120 Mo not
released.
If I use 300 files, the memory goes up to 35 Mo. If I put 600 files, it
grows to 55 Mo. But, if I put 300 files, let the program roll and put again
300 files, I see the memory growing up to 35 Mo the first time, and when I
put the next 300, the memory is still at 35 Mo, but it doesn't grow anymore.
nos, if I place 300 files, and then 600, the memory grows up for the first
300, then stays still for the next 300 and then starts growing again for the
last 300.
It acts like when it processes files continuously, it can't free the memory.
But if I "let it breath" and give it some more files, the memory is somehow
"reused" for the same amount of memory...
Does anybody have any idea where this behavior can come from??
Yes. It sounds like this is the AIX C run-time heap causing this
behavior. There are AIX heap debug routines and environment variables
that can help you:
http://www.redbooks.ibm.com/redbooks/pdfs/sg245674.pdf
Read chapter 4 for more information.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
