c# allocate memory and assign a different variable

Question

This is a very basic question, but I thought better to ask. Let us assume I have the following code snippet.

List<String> mystringlist1 = new List<String>();

List<String> mystringlist2 = new List<String>();
mystringlist2.Add("hello1");
mystringlist2.Add("hello2");
mystringlist2.Add("hello3");

//Now I assign the second list to first list
mystringlist1 = mystringlist2;

Now as it stands, both the lists will be pointing to the same memory location and trying to access the individual elements will result in the same elements of the above list.

If so,

what would have happened to the unclaimed/unused allocation which was done for mystringlist1?
Will this be automatically garbage collected or will it result in memory leaks?
Is it a bad practice to do this?

Brian Rasmussen · Accepted Answer · 2014-06-07 05:10:56Z

3

What you're doing is perfectly fine. In fact, that's the scenario the language and the runtime was designed to handle. You don't explicitly allocate and free memory. Instead you create instances and once these are no longer used the garbage collector will reclaim the associated memory.

As you assign mystringlist1 = mystringlist2 the instance that mystringlist1 pointed to becomes eligible for garbage collection. It means that if a garbage collection is triggered the memory will be reclaimed.

answered Jun 7, 2014 at 5:10

Brian Rasmussen

117k34 gold badges227 silver badges325 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Muthu Over a year ago

Thanks. Both yours as well as Bradley's were good answers. But I could select only one as answer & upvoted yours.

BradleyDotNET · Accepted Answer · 2014-06-07 05:08:59Z

2

It will be garbage collected
Yes it is automatic
Yes it is bad practice to allocate something you never use. If you are going to use it for something, allocate and reassign away. There is no reason to randomly instantiate stuff though.

Note that it will be collected on the next pass of the Garbage Collector for its generation. Since it wasn't around very long, it should still be in Gen0 and be collected fairly quickly. This isn't true for all variables, so it may look like there is a memory leak when there really isnt.

The other exception is anything that uses unmanaged memory (like Bitmap) which need to be disposed after use.

answered Jun 7, 2014 at 5:08

BradleyDotNET

61.5k10 gold badges106 silver badges124 bronze badges

1 Comment

BradleyDotNET Over a year ago

Would the downvoter care to comment what problem you had with my answer?

Collectives™ on Stack Overflow

c# allocate memory and assign a different variable

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related