We don't have any memory leak. At exit application all memory
is correctly released.
Our applications run correctly during many hours and days in
largely of computers, but those with memory problems, which is
where this is critical memory usage.
It's simple check with :
Memory( HB_MEM_USED )
All people can try this, normally goes correctly but in some cases
depending of the architecture of application, MDI Child don't free
all memory. Why ? is the question :)
I make some tests more to find the guilty...
And, What about ...
Rare something was happening and I need to check if the problem persists.
Debugger of the Borland showed a stack of calls incorrect when there was
a GPF,
this happened when it created definitions of functions between methods
of a class.
The stack showed the first function that nobody had called, but seemed
to run the
correct method apparently.
Rare !!!!
Best regards,
Miguel Angel Marchuet
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
xHarbour-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
