From: wajnberg AT antibes DOT inra DOT fr (Eric Wajnberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Rhide and free available memory
Date: 21 Mar 2001 13:13:35 GMT
Organization: I.N.R.A. Antibes (France) - Ecologie des Parasitoides
Lines: 35
Message-ID: <99a9dv$3jk$1@saphir.jouy.inra.fr>
References: <3AB8C070 DOT 535 DOT 1E05C2 AT localhost>
NNTP-Posting-Host: antibes.inra.fr
X-Trace: saphir.jouy.inra.fr 985180415 3700 195.221.33.1 (21 Mar 2001 13:13:35 GMT)
X-Complaints-To: usenet AT news DOT inra DOT fr
NNTP-Posting-Date: 21 Mar 2001 13:13:35 GMT
X-Newsreader: TIN [version 1.2 PL2]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

pavenis AT lanet DOT lv wrote:

: There are memory leaks, especially in debugger part. One can easily 
: test it under Linux with gdb by setting executable to be debugged
: with command file multiple times and looking how much memory gdb 
: takes. So if RHIDE takes too much memory, then simply restart RHIDE


I am not using Rhide on Linux, but under Windows98. I indeed observed that
restarting Rhide could refresh a little bit (but not always) the memory
indication. Restating Windows itself could also be of some help sometimes.
However, all of this looks like been quite eratic. And this keep on
surprising me all the time.

All of this could just be a curiosity, but this is currently making me anxious
since I am approaching the upper limit of memory available under my
environment..

Thanks for any additional help on this.

Eric


    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   
    Eric Wajnberg
    Directeur adjoint du GDR CNRS 2155 Ecologie Comportementale
    I.N.R.A.
    37, Bld. du Cap. 06600 Antibes. France.
    Tel : (33-0) 4.93.67.88.92
    Fax : (33-0) 4.93.67.88.97
    e-mail : wajnberg AT antibes DOT inra DOT fr

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~