When you start a program and then quit it, the Free System Resources value
may not return to the same value as before you started the program.
There are two possible explanations for this behavior:
- System Initialization
Windows defers much of system initialization until the first time
a program asks for a particular service. For example, each font is
initialized when a program first asks for it, rather than initializing
all fonts at system startup (as in Windows 3.1).
If a program requests a service that uses deferred initialization, the
service remains initialized after the program has exited. The system
resources associated with that service are not freed. The system keeps
the service initialized so that the next program that requests the
service does not have to wait for the service to be initialized.
This behavior is by design.
- Compatibility
For compatibility reasons, Windows does not free system resources
abandoned by Windows 3.1-based programs until all Windows 3.1-based
programs have been closed. Only when there are no Windows 3.1-based
programs running can Windows safely release abandoned system
resources.
If you close all Windows 3.1-based programs but the behavior continues, restart Windows.