Board index » delphi » Changing screens and click buttons uses and doesn't return memory

Jeshua

Delphi Developer
Sat, 17 Jan 2004 08:54:02 GMT

Changing screens and click buttons uses and doesn't return memory

I have a application that when clicking buttons and opening screens the memory (viewed via task manager in Win NT4) goes up.  When I return to the main screen the memory doesn't return to what it was before clicking or changing screens.  I have used memory sleuth from turbopower but it doesn't report any changes!  Does anyone know what may be happening.  I'm using Delphi 4.  This application is a long term run app so several months maybe required and increases in memory usuage is a concern.

 
Flavius Vespasianu

Delphi Developer
Sat, 17 Jan 2004 09:56:19 GMT

Re:Changing screens and click buttons uses and doesn't return memory


"Jeshua" <jesh...@elpro.com.au> wrote in news:3b6601aa$1_2@dnews:

Quote

> I have a application that when clicking buttons and opening screens the
> memory (viewed via task manager in Win NT4) goes up.  When I return to
> the main screen the memory doesn't return to what it was before
> clicking or changing screens.  I have used memory sleuth from
> turbopower but it doesn't report any changes!  Does anyone know what
> may be happening.  I'm using Delphi 4.  This application is a long term
> run app so several months maybe required and increases in memory usuage
> is a concern.

Memory allocators generally work by enlarging the virtual address space to
create large chunks of memory. From these, it allocates and returns the
chunks for applications. The allocators generally do not shrink the virtual
address space once memory is returned.

If your memory sleuth says you are not losing memory then take its word.

Jeshu

Delphi Developer
Sat, 17 Jan 2004 10:44:01 GMT

Re:Changing screens and click buttons uses and doesn't return memory


Thanks,

That makes sense.  Another interesting thing I found was that when
minimising lots of memory was returned and maximising brought the levels up
again (but not to the same level).  I suppose that the virtual memory is
returned when minimising and as the app requires it more memory is
allocated.

Quote
"Flavius Vespasianus" <n...@nl.com> wrote in message

news:3b661043$1_2@dnews...
Quote
> "Jeshua" <jesh...@elpro.com.au> wrote in news:3b6601aa$1_2@dnews:

> > I have a application that when clicking buttons and opening screens the
> > memory (viewed via task manager in Win NT4) goes up.  When I return to
> > the main screen the memory doesn't return to what it was before
> > clicking or changing screens.  I have used memory sleuth from
> > turbopower but it doesn't report any changes!  Does anyone know what
> > may be happening.  I'm using Delphi 4.  This application is a long term
> > run app so several months maybe required and increases in memory usuage
> > is a concern.

> Memory allocators generally work by enlarging the virtual address space to
> create large chunks of memory. From these, it allocates and returns the
> chunks for applications. The allocators generally do not shrink the
virtual
> address space once memory is returned.

> If your memory sleuth says you are not losing memory then take its word.

Other Threads

1. W95: Application button text on taskbar doesn't change

2. I can't get Screen.OnActiveFormChange to fire when not using a mouse click

3. I can't get Screen.OnActiveFormChange to fire when not using a mouse click

4. TListView, OwnerDraw, Font size is changed ,but the Items size doesn't change

5. DBLookupComboBox Click event doesn't work!

6. D5: Popup menu doesn't close when item clicked

7. MDI Child doesn't close when ApplicationMenu Close() is clicked

8. D5: Popup menu doesn't close when item clicked

9. Dbl-click doesn't work in DBCtrlGrid!

10. Application doesn't go in the taskbar when I click on minimize