[DUG] D2006/Rave/Memory

[John Bird]

I think I have finally proved my memory woes are caused by BDS - I just had
the PC running slow, according to sysinternals System Information it was
using 955MB of ram (system memory is 768MB hence everything started
crawling), on closing BDS it immediately dropped to 355MB.  I had my big
project open (with RvSystem) but first I closed it and opened a small
project - it didn't free up any memory, but closing BDS did.
 
Any suggestions?
 
Otherwise I think its off to the shop to upgrade memory to 1GB (maximum this
system takes). Dunno if that will fix it tho!
 

John 

 -----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz] On
Behalf Of John Bird
Sent: Tuesday, 4 July 2006 10:34 a.m.
To: 'NZ Borland Developers Group - Delphi List'; delphi at delphi.org.nz
Subject: [DUG] D2006/Rave/Memory



I am having frequent instances of my PC running out of memory and coming up
with messages about "Windows has run out of virtual memory and is increasing
the page file size"  The hard disk goes crazy, the pc slows to a crawl and
usually the Windows session goes cuckoo after that, even exiting programs to
lessen memory use can take forever, and usually the best is to reboot.  I
have tried to narrow it down - Firefox with lots of tabs? well I tried Opera
instead and IE7.
 
I have no proof but my best guess so far is BDS 2006 with a project open
using Rave Reports - it only started happening after I used Rave in a few
projects.  Projects without it I think are be OK.  I am only using the
RvSystem component for code based reports, although it is quite large - it
adds some 800K to the program.  Rebuild such a project a few times over a
few hours, and it seems the system runs out of memory.  This is without
running the Rave printing at all  - I am testing other stuff, also using the
debugger.  Process explorer doesn't show any obvious candidate.  Or
alternatively it could be any component with large memory usage - Rave is
the only one I use of such size.  Or maybe the debugger is another candidate
(I often run programs with a few breakoints set to check some variable
values, thats pretty much all I do with it).
 
Anyone else have any similar experience?
 
The system is Windows XP SP2, 768MB Ram,  over 2GB free disk, have
defragmented recently (it seems to help a lot), have sysinternals
Processexplorer (thumbs up).

John

 



__________ NOD32 1.1461 (20060329) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ns3.123.co.nz/pipermail/delphi/attachments/20060705/a315b926/attachment.html