Table of Content
- Abstract Classes
- Access Specifiers
- ASP.NET 2.0 Interview Questions
- Assembly and Namespaces
- Authentication in .Net
- Authorization in .Net
- Boxing vs Unboxing
- Const vs Read-only
- Const vs Read-only
- Constants in .Net
- Constructors
- Constructors of Extended Classes
- Cursor point to TextBox
- Data Abstraction
- Data Encapsulation
- Destructors
- Example on Encapsulation
- Fields in .Net
- Focus method
- Function Overloading
- Garbage Collections
- Gridview with Paging
- Indexers in .Net
- Inheritance and Extended Classes
- Inheritance in .Net
- Inheritance n Extended Classes
- Members of a Class
- Methods and Events
- Namespace used in EventLog
- Object
- Overriding and Hiding
- Page Life Cycle
- Properties in .Net
- Ref vs Out parameter
- Server.transfer vs Response.redirect
- Signatures of Main[] fn
- State Management
- String vs String Builder
- Types of parameters
- Using Keyword
- Value type vs Ref type
- Versioning in .Net
- What are Class Methods
- What are Classes
- What are Constructors
- What are Delegates
- What are Objects
- What is View State
- When to OverLoad
Friday, June 4, 2010
What is Garbage Collections
The >Net Framework's garbage collector manages the allocation and release of memory for your application. Each time you create a new object, the common language runtime allocates memory for the object from the managed heap. As long as address space is available in the managed heap, the runtime continues to allocate space for new objects. However, memory is not infinite. Eventually the garbage collector must perform a collection in order to free some memory. The garbage collector's optimizing engine determines the best time to perform a collection, based upon the allocations being made. When the garbage collector performs a collection, it checks for objects in the managed heap that are no longer being used by the application and performs the necessary operations to reclaim their memory.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment