Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5964177
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T19:23:05+00:00 2026-05-22T19:23:05+00:00

I understand that only way a .NET application ( that does not use any

  • 0

I understand that only way a .NET application ( that does not use any unamanged code) can cause memory fragmentation is by large object heap. Are there any ways of detecting if your application is fragmenting memory and anyways of avoiding it?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T19:23:05+00:00Added an answer on May 22, 2026 at 7:23 pm
    1. Keep objects small.
    2. Keep objects short-lived.
    3. Trust the GC

    1 and 2 might be tough in practice but honestly, you’d be talking about BIG objects and the GC really does a good job with all this.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I understand that .NET FileStream's Flush method only writes the current buffer to disk,
For reasons that only the developers can understand, Firefox will create and open .url
Trying to implement a MSMQ-backed WCF PubSub. I understand that net.msmq is one-way; however
The .NET application for which I'm responsible uses a third-party control that is only
I understand that TempData is designed to work only between a single page request.
Am I correct to understand that the abort() method for XMLHttpRequest objects is only
As I understand it, Domain Models are classes that only describe the data (aggregate
Why only one overload throws this exception? Little update: I understand that there was
I need to change the code of some asp.net application but the application is
I have an ASP.NET MVC application that has a jQuery Treeview and a jQuery

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.