VS Diagnostic Tools Shows that the memory consumed while creating a DataTable is not released even after GC.Collect()

Question

VS Diagnostic Tools Shows that the memory consumed while creating a DataTable is not released even after GC.Collect().

Code Snippet:

using (DataTable table = new DataTable())
{
for (int column = 0; column < 1024; column++)
{
table.Columns.Add("Name" + column);
}
for (int row = 0; row <= 75000; row++)
{
table.Rows.Add();
for (int column = 0; column < 1024; column++)
{
table.Rows[row][column] = "Kim" + row + column;
}
}
}
GC.Collect();

Answer 1

A datatable is a resource hog and you're working with 75,000 rows. Maybe you should consider using a collection with a custom class.

http://lauteikkehn.blogspot.com/2012/03/datatable-vs-list.html

https://learn.microsoft.com/en-us/dotnet/visual-basic/programming-guide/concepts/collections

https://learn.microsoft.com/en-us/dotnet/visual-basic/programming-guide/language-features/procedures/auto-implemented-properties

Answer 2

GC.Collect() cannot guarantee that all memory will be collected.

Use this method to try to reclaim all memory that is inaccessible. It performs a blocking garbage collection of all generations.

All objects, regardless of how long they have been in memory, are considered for collection; however, objects that are referenced in managed code are not collected.

You can also take a look at the discussion on this issue in this post:

.NET Garbage Collection behavior (with DataTable obj)

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.