OK,
this is the first reply to this issue......
But we are here in the non-technical aera......!!!!! where I asked for
a non technical question....
and you will find ATTACHED a project group with projects given using
the delphi 5 demo source...
copy simple the unzipped test4711.zip (2k in size) to the demo path!
Use W2k Sp1 with 128 mbytes :
- open task manager
- open delphi with the test4711 group and have then 22 Mbytes memory
used
- build full group and have finnaly have used 60Mbytes (this will go
worst depended of the source size and project count count
A suggestion for Borland news group :
a) a pure bug discussion area
b) a pure suggestion area
c) open access to the bug database
d) give REAL answer to given bug reports
(not automatically generated only)
cheers
HpW
Swedish? Maybe even KTH?
--
Anders Ohlsson
Borland(R) Delphi(TM) Developer Support
Inprise Corporation
http://homepages.borland.com/aohlsson/
http://homepages.borland.com/aohlsson/Halloween.jpg
http://homepages.borland.com/aohlsson/Thanksgiving.jpg
http://homepages.borland.com/aohlsson/disclaimer_ani.gif
http://homepages.borland.com/aohlsson/disclaimer.gif
ShowMessage(^ ^%^.^$^`^-^%^`^9^/^5^2^`^2^%^3^5^-^%);
>ATTACHED
a) *NEVER* attach anything to any message.
http://www.borland.com/newsgroups/guide.html#rules
b) I have a kill filter on attachments - I will never see *any* postings
that contain attachments.
Everyone is free to send me stuff via email (try "stefan" with the domain
"econos.de") if, only if, and when it is clear that I really want to have
something. If it's not clear, ask before sending stuff.
IOW, please send me the files via *email*. Thank you.
>- open delphi with the test4711 group and have then 22 Mbytes memory
>used.
Ok.
>- build full group and have finnaly have used 60Mbytes (this will go
>worst depended of the source size and project count count
Sure - unit caching. Now, if that increased steadily from 60 MB, and if it
didn't drop back with a new project group, then this would be a leak.
I just recorded the following memory used amounts, as reported by Task
Manager:
Delphi after startup: 192 MB
After "compile all" (5 projects in group): 292 MB
Switch to another project group: no change
Compile all with new group: 295 MB
IOW, compile all used 100 MB, which was not released when a new project
group was loaded. However, it did seem to be re-used on the next compile.
Why would units (or anything else, for that matter) need to be cached to
this extent after a compile? My memory "limit" is around 310 MB, according
to task manager. I quite frequently surpass that figure (and get a dialog
box talking about increasing virtual memory) during a large compile or build
all. I'd much rather have the compile, link, or whatever take a little
longer as opposed to using up all my memory until I shut down Delphi.
btw: system is
W2K sp1
128 MB RAM
333 mHz PII
brian
"R. Brian Lindahl" wrote:
>
> > >- build full group and have finnaly have used 60Mbytes (this will go
> > >worst depended of the source size and project count count
> >
> > Sure - unit caching. Now, if that increased steadily from 60 MB, and if it
> > didn't drop back with a new project group, then this would be a leak.
>
> I just recorded the following memory used amounts, as reported by Task
> Manager:
>
> Delphi after startup: 192 MB
> After "compile all" (5 projects in group): 292 MB
> Switch to another project group: no change
> Compile all with new group: 295 MB
>
> IOW, compile all used 100 MB, which was not released when a new project
> group was loaded. However, it did seem to be re-used on the next compile.
>
Try minimizing Delphi between the two compiles. Task Manager is not a memory
leak detector and was never intended to be used as such. All it reports is the
amount of available memory. Freeing memory does not force Windows to reclaim it
immediately and therefor the task manager seems to be reporting a leak. A few
events will cause windows to sweep the heap and reclaim freed memory.
Minimizing the main window of an app is one of these events.
For example. I have a project that task manager starts at 6,448 KB used. After
compile it is 39,036. Compile again it is 39,232. Now minimize Delphi and have
the Windows memory manager sweep for freed memory by Delphi and it drops back
down to 1,764 and restore Delphi and it goes right back to 6,260 (this sometimes
takes 30-60 seconds after the compile for windows to actually catch it for
sweeping).
What you are seeing is the effect of Windows not returning freed memory
immediately to the heap which is what the Task Manager is monitoring. Stefan is
correct that Delphi does cache the units until all the builds are done, but that
memory is released after all the projects are compiled.
> Why would units (or anything else, for that matter) need to be cached to
> this extent after a compile?
It isn't, only cached during the compile of all the projects. See above.
> My memory "limit" is around 310 MB, according
> to task manager. I quite frequently surpass that figure (and get a dialog
> box talking about increasing virtual memory) during a large compile or build
> all. I'd much rather have the compile, link, or whatever take a little
> longer as opposed to using up all my memory until I shut down Delphi.
>
> btw: system is
>
> W2K sp1
> 128 MB RAM
> 333 mHz PII
>
> brian
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
The fool escaped from paradise will look over his shoulder and cry
Sit and chew on daffodils and struggle to answer why?
As you grow up and leave the playground
Where you kissed your Prince and found your frog
Remember the jester that showed you tears, the script for tears. (Fish)
>Why would units (or anything else, for that matter) need to be cached to
>this extent after a compile?
Performance - fast code completion, tooltip symbol insight, linking, ...
>My memory "limit" is around 310 MB, according
>to task manager. I quite frequently surpass that figure (and get a dialog
>box talking about increasing virtual memory) during a large compile or build
>all.
Suggestion: Increase the size of your swap file - yes, this is only a
work-around.
>I'd much rather have the compile, link, or whatever take a little
>longer as opposed to using up all my memory until I shut down Delphi.
IOW, less aggressive caching?
Could you characterize the project group you have trouble with, together
with your D5 environment?
> Delphi after startup: 192 MB
Let me characterize mine:
Memory usage as indicated by the W2K SP1 task manager after startup of D5
SP1: 153 MB. *But* I have running
* three instances of Forte Agent
* four instances of IE 5.0
* ZoneAlarm
* a TV viewer
* LeechFtp
* a largish application
Please do not misunderstand me, but looking at the information you
supplied
> Delphi after startup: 192 MB
> 128 MB RAM
your system is by far too overloaded.
An aside question: How did you attach that? My newsreader
thingie is *not* set up to get attachments, but I got this one
anyway...
>> 4711
>
>Swedish? Maybe even KTH?
4711 is the number of the original "Eau de Cologne". The company is in
4711 Glockengasse, Cologne.
--
Rudy Velthuis (TeamB) http://delphi-jedi.org
Use Borland servers; TeamB don't see posts via ISPs
http://www.borland.com/newsgroups/genl_faqs.html
That's true, but I haven't seen it in heavy use other than at my school
in Stockholm, Sweden. 17 and 4711 are their favorite "random" numbers.
>That's true, but I haven't seen it in heavy use other than at my school
>in Stockholm, Sweden. 17 and 4711 are their favorite "random" numbers.
Here in Germany, people use 4711 as a "cute" number, e.g. on number
plates. Here it definitely means the Cologne.
Oh well... So much for being "special"... <g>