.NET garbage collector question when circular references exist

Question

I know that the .net garbage collector detects circular references, but I was wondering if circular references could cause objects to stay longer than necessary.

I have a circular reference in my ASP.NET application (intended for performance reasons), can I handle this?

Hello

Answer 1

CLR , . CLR . , ( GC). , , . . , CLR,

Answer 2

, .

( , , , , GC'ed) , , GC'ed.

, GC. . , , .

Answer 3

, - , , - , . , . , , .

, (-), .

Answer 4

GC , . , (, / ), , , CPU.

GC , " ". , , , .

, ( ) root, , . . , , GC , .

, . , , , .. , .NET. , , CLR .

MSDN - Garbage Collector Basics and Performance Recommendations (Rico Mariani)

MSDN Magazine - Garbage Collection (Part 1): Automatic Memory Management in the Microsoft .NET Framework (Jeffrey Richter)

MSDN Magazine - Garbage Collection (Part 2): Automatic Memory Management in the Microsoft .NET Framework (Jeffrey Richter)

Answer 5

Java GC can detect loops and process them. I would argue that C # GC can also.