If the program aborts with an error, I closed it via the (X) in Windows (system close) or just exit the application in a normal way the process image remains in memory. Is this normal behavior ? Thank you.
FiveTech Support Forums
FiveWin / Harbour / xBase community
Board index FiveWin for Harbour/xHarbour Process remains in memory.
No, try the following sample:
EMG
#include "Fivewin.ch"
FUNCTION MAIN()
LOCAL oWnd
DEFINE WINDOW oWnd
ACTIVATE WINDOW oWnd
RETURN NILEMG
Enrico:
With your sample program the image is discarded from memory as soon as the program exits. Now, I define a Window, Menu and the image remains in memory. Basically it's a indexing program. You select the file and it recreates all indexes. No external resources, DLLs, etc. Pretty simple program. Thank you for your help.
How do you exit from your application ?
Please show us your code or a working sample that has the same behavior, thanks
Hello Antoinio,
In some samples I see following code:
EXIT PROCEDURE PrgExit
Set RESOURCES TO
GlobalFree()
ResAllFree()
Release All
SysRefresh()
Clear Memory
RETURN
Do you suggest to use such a procedure?
Thanks in advance
Otto
Otto,
It is not needed at all. FWH and Windows automatically take care of those tasks.
Antonio: thank you for your support. Doing some test before sending you the sample code, I found out that if I got a LOCAL variable called cString the program image remains in memory. I dropped that variable and the images left memory when exiting or closing the program.
???
Try the following sample:
EMG
Try the following sample:
#include "Fivewin.ch"
FUNCTION MAIN()
LOCAL oWnd
LOCAL cString
DEFINE WINDOW oWnd
ACTIVATE WINDOW oWnd
RETURN NILEMG
Thank you Enrico. But the only thing I did was removing this cString variable and everything worked out. If I define it as a LOCAL the problems comes back.
Did you try my sample? Otherwise, can you build a minimal sample showing the problem?
EMG
What are the contents of the local cString variable ?
We have never seen something like that before. Very strange.