Page 1 of 1

Process remains in memory.

Posted: Tue Jun 03, 2008 2:42 pm
by HunterEC
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.

Re: Process remains in memory.

Posted: Tue Jun 03, 2008 3:41 pm
by Enrico Maria Giordano
No, try the following sample:

Code: Select all

#include "Fivewin.ch"

FUNCTION MAIN()

    LOCAL oWnd

    DEFINE WINDOW oWnd

    ACTIVATE WINDOW oWnd

    RETURN NIL
EMG

Posted: Wed Jun 04, 2008 4:22 am
by HunterEC
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.

Posted: Wed Jun 04, 2008 6:50 am
by Antonio Linares
How do you exit from your application ?

Please show us your code or a working sample that has the same behavior, thanks

Posted: Wed Jun 04, 2008 8:03 am
by Otto
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

Posted: Wed Jun 04, 2008 9:55 am
by Antonio Linares
Otto,

It is not needed at all. FWH and Windows automatically take care of those tasks.

The xFiles (ha,ha,ha)

Posted: Wed Jun 04, 2008 11:08 pm
by HunterEC
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.

Re: The xFiles (ha,ha,ha)

Posted: Thu Jun 05, 2008 6:53 am
by Enrico Maria Giordano
???

Try the following sample:

Code: Select all

#include "Fivewin.ch" 

FUNCTION MAIN()

    LOCAL oWnd

    LOCAL cString

    DEFINE WINDOW oWnd

    ACTIVATE WINDOW oWnd

    RETURN NIL
EMG

Posted: Thu Jun 05, 2008 7:23 am
by HunterEC
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.

Posted: Thu Jun 05, 2008 7:26 am
by Enrico Maria Giordano
Did you try my sample? Otherwise, can you build a minimal sample showing the problem?

EMG

Posted: Thu Jun 05, 2008 7:27 am
by Antonio Linares
What are the contents of the local cString variable ?

We have never seen something like that before. Very strange.