Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows XP / General Topics 1 / May 2008

Tip: Looking for answers? Try searching our database.

Unload Unnecessary DLLs From Memory - Good Idea?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Daddy - 26 May 2008 02:19 GMT
I have Windows XP Home SP 3.

Normally, when you close a program, any associated DLLs it has been using should also be closed.

I have read that this doesn't always happen - sometimes DLLs no longer needed are not closed - and that this can result in a sluggish and unstable system. There is a registry edit published to allegedly fix this problem: In HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer you create a new DWORD value called AlwaysUnloadDll and give it a value of 1. This is supposed to ensure that unneeded DLLs are always unloaded from memory when their associated program closes.

I like to think I have a pretty advanced level of knowledge, and I've certainly worked in the registry before, but I do like to be very cautious just the same. So before I even consider doing this, I want to ask about it first.

Is this 'problem' really such a problem?

Does the proposed fix have a dark side?

Thanks for your candid advice.

Daddy
Bill in Co. - 26 May 2008 02:32 GMT
> I have Windows XP Home SP 3.
>
> Normally, when you close a program, any associated DLLs it has been using
> should also be closed.
>
> I have read that this doesn't always happen

Right.

> - sometimes DLLs no longer needed
> are not closed

Who is to know for sure that it isn't really needed anymore?    Which
program is omnipotent enough to make that call?

>- and that this can result in a sluggish and unstable system.

Balderdash.

> There is a registry edit published to allegedly fix this problem: In
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer you create a new
[quoted text clipped - 10 lines]
>
> Is this 'problem' really such a problem?

No.

> Does the proposed fix have a dark side?

Yes, potentially.    Just like the so called "registry cleaners" (cough).

> Thanks for your candid advice.
>
> Daddy
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.