Not AFAIK. I periodically shut down BCB and restart it. :-(
--
Kent (TeamB and TurboPower Software)
Ken Moffat
kmo...@halcyon.com
> I left Borland C++ builder 4.0 60 Day trial running for 24 hours (just
> sitting there idle after building a small project), and when I came back
> my virtual memory usage was 250 MB, with 94 MB for bcb.exe. Has this
> been fixed in the non trial version?
Haven't tried this, but BCB4 doesn't leak out of your compiled .EXEs,
unlike the previous versions : ¬ )
AlisdairM
>Haven't tried this, but BCB4 doesn't leak out of your compiled .EXEs,
>unlike the previous versions : ¬ )
<cough>
http://www.nidlink.com/~astoyanov/index.htm
lists Delphi 4.0 leaks. C++Builder 4.0 has about the same leaks.
--
Stefan Hoffmeister (TeamB) http://www.econos.de/
Please do apply judgement when sending email.
> >Haven't tried this, but BCB4 doesn't leak out of your compiled .EXEs,
> >unlike the previous versions : ¬ )
>
> <cough>
>
> http://www.nidlink.com/~astoyanov/index.htm
>
> lists Delphi 4.0 leaks. C++Builder 4.0 has about the same leaks.
Thanks, I'll check out the link!
I stand corrected, but both my memory leak detection packages give it a
clean bill of health, so all that is left is my own leaks! This has
made 'plugging' a lot easier!
AlisdairM
BTW,
Packages I am using are BoundsChecker 5.03 and MemorySleuth 1.03, both
shipped with earlier versions of BCB, and appropriate free
patches/upgrades for BCB3 (not 4 yet) applied
>I stand corrected, but both my memory leak detection packages
Memory Sleuth is not the only resource tracker on the market.
>give it a
>clean bill of health, so all that is left is my own leaks! This has
>made 'plugging' a lot easier!
>
>Packages I am using are BoundsChecker 5.03
...which in my experience is <censored> as far as the Borland memory
manager is concerned.