Re: Garbage Collection and Library Deployment
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Fri, 20 Feb 2009 12:12:55 -0800
On Fri, 20 Feb 2009 12:02:18 -0800, Trecius <Trecius@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
[...] Because RAM is a valuable
resource for my low-end system, I call GC.Collect() and
GC.WaitForPendingFinalizers() AFTER CALLING MY METHOD, which the array is a
LOCAL variable to the method. However, looking at Task Manager, the RAM is
not released, and my application is still consuming approximately 350 MB of
RAM. Am I missing something?
Here's a sample of my code...
void MethodToCreateLargeArray()
{
object[] rgLargeArray;
// CREATE AND POPULATE rgLargeArray
}
void SomeMethod()
{
this.MethodToCreateLargeArray();
GC.Collect();
GC.WaitForPendingFinalizers();
}
That's it.
Well, you left out all the interesting parts, replacing them with a comment.
But, most likely you're just seeing normal .NET behavior. Just because you're done with the memory, that doesn't mean .NET releases the OS allocation it made in order to satisfy your need. That would be inefficient. Instead, it will continue to keep that allocation, in case you wind up allocating another huge structure again.
In general, you should not call GC.Collect() or GC.WaitForPendingFinalizers(). They are unnecessary, and usually will have counter-intuitively detrimental effects on your program's performance. For managing GC behavior, it's much more likely that you'd use the Thread.BeginCriticalRegion()/EndCriticalRegion() methods, and even that's a very rare need.
Just because RAM is "a valuable resource for your low-end system", that doesn't mean your program should be explicitly trying to manage it. Let ..NET and Windows do their job, and focus on the stuff your program actually has to do.
My second question has to do with building libraries. I have built a
library that I would like to distribute. When building the library, I ensure
the IDE is set to RELEASE. However, I've noticed that when I am using my own
library that I built in a separate project when my new application makes a
call to the library and the library has an exception, I can see all of my
code that I wrote for that library. How can I build my library that would
not allow people to see my code when the library throws an exception in debug
mode?
That depends on what you mean by "see all of my code". From your description, it sounds like you are looking at it in the debugger. If so, then all you need to do to prevent others from seeing the code is to not deliver a .pdb file and the source code along with your library.
Someone will still be able to use a tool like Red Gate's Reflector to decompile the code, but that won't be a literal representation of your actual code (e.g. no comments, variable names might be different, implementation details that are provided by the compiler may appear, etc.)
Pete
.
- Follow-Ups:
- Re: Garbage Collection and Library Deployment
- From: Trecius
- Re: Garbage Collection and Library Deployment
- References:
- Garbage Collection and Library Deployment
- From: Trecius
- Garbage Collection and Library Deployment
- Prev by Date: Garbage Collection and Library Deployment
- Next by Date: C# Excel COM lib: Getting last row of data in a column...
- Previous by thread: Garbage Collection and Library Deployment
- Next by thread: Re: Garbage Collection and Library Deployment
- Index(es):
Relevant Pages
|
