Welcome Guest.   Make a donation to an author on the site October 21, 2014, 12:23:34 AM  *

Please login or register.
Or did you miss your validation email?


Login with username and password (forgot your password?)
Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.


You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.
 
Learn about the DonationCoder.com microdonation system (DonationCredits).
   
   Forum Home   Thread Marks Chat! Downloads Search Login Register  
Pages: [1]   Go Down
  Reply  |  New Topic  |  Print  
Author Topic: Memory Usage  (Read 3098 times)
Grorgy
Supporting Member
**
Posts: 820

see users location on a map View Profile Give some DonationCredits to this forum member
« on: May 04, 2007, 04:37:26 AM »

This may be covered elsewhere but i couldnt see it so here i go

I have started playing around with this now and I have it set to start minimized.  Everything is fine and it works really well but until you maximise and then minimise it, i've discovered that the memory usage stays quite high, compared to what it is when normally lying at rest in that thing we dare not call a tray.

Just to let you know if you didnt and no one else has mentioned it.

Ohh i saw screenshot captor over at VNUNet.com , they gave it 5 stars and said what a great program it was  Thmbsup
Logged
mouser
First Author
Administrator
*****
Posts: 33,571



see users location on a map View Profile WWW Read user's biography. Give some DonationCredits to this forum member
« Reply #1 on: May 04, 2007, 07:55:27 AM »

Thanks for pointing this out -- I will add a feature i add to most of my programs that let's you choose whether you want them to release their working memory when minimized.  thumbs up
Logged
superticker
Supporting Member
**
Posts: 138


View Profile WWW Give some DonationCredits to this forum member
« Reply #2 on: June 14, 2007, 12:20:26 PM »

I will add a feature i add to most of my programs that let's you choose whether you want them to release their working memory when minimized.

I think it's standard practice to have Windows apps release their memory (like for their GUI) in the free-memory pool when they're minimized and the zero-page pool if they never need that memory again.  Understand, the first pool is for temporarily releasing memory that otherwise needs to be reclaimed when restoring the app to the desktop.  The idea is that if no other programs need that space, then those pages remain available to the app that originally released them when it gets restored; (otherwise, those free pages can made available to external apps instead of calling the swapper).

The zero page pool is for permanently releasing memory (never to be reclaimed in the future).  The OS immediately writes zeros in these pages (to prevent browsing) so they can be immediately allocated to unrelated processes.
Logged
Pages: [1]   Go Up
  Reply  |  New Topic  |  Print  
 
Jump to:  
   Forum Home   Thread Marks Chat! Downloads Search Login Register  

DonationCoder.com | About Us
DonationCoder.com Forum | Powered by SMF
[ Page time: 0.023s | Server load: 0.08 ]