Garbage Collector Static Fileds

Question

0.00/5 (No votes)

See more:

Hi,

If i have a class with some statics filed like below:

C#

class Test{

public static SomeotherClass _someotherclassObj=new SomeotherClass();

//other members and method..

}

If i have 100 instances of class Test, will those instances will be marked reachable by Garbage Collector (because of static member) and will remain till application ends.

Thanks!!
Rahul

Posted 2-Apr-12 17:38pm

Rahul83

Updated 2-Apr-12 17:45pm

member60

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**JF2015** · Answer 1 · 2012-04-02T17:52:00

Solution 1

Static objects are always marked to be NOT garbage collected until they are set to NULL.
Here is a nice article that explains a bit more about the topic:
http://msdn.microsoft.com/en-us/magazine/bb985010.aspx[^]

Posted 2-Apr-12 17:52pm

JF2015

member60 · Answer 2 · 2012-04-02T17:53:00

Objects referenced by static variables will only be garbage collected when the relevant AppDomain is garbage collected. In client applications, there's often just a single AppDomain which lives for the duration of the process. (An exception is when the application uses a plug-in architecture - different plug-ins may be loaded in different AppDomains and the AppDomain may be unloaded later.)

In ASP.NET, "AppDomain recycling" happens periodically (for various reasons) - when this occurs, and the static variables within that AppDomain will no longer act as GC roots, and thus won't prevent objects being garbage collected.

If you were worried about an object being garbage collected while you still had a reference to it via a static variable, though, you can relax. While you can access the object, it won't be garbage collected.