Home/ Questions/Q 7490635
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T15:41:24+00:00

Andrew Troelsen in his book Pro C# 2008 and the .NET 3.5 Platform, Fourth

  • 0

Andrew Troelsen in his book Pro C# 2008 and the .NET 3.5 Platform, Fourth Edition says while explaining newobj instruction from CLR page no. 248, first para third bullet

before returning the reference to the caller, advance the next object pointer to point to the next available slot on the managed heap

sounds like advance the next object pointer is winthin a lock block (or something similar) to make sure this pointer gets incremented correctly after every object creation on managed heap by all .net threads. Am i right or entirely wrong?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First of all this is an implementation detail. There are many ways to implement this, and a CLR implementation is free to choose whichever it likes.

    A few possible implementations:

    1. Use locking as you suggest
    2. Use ” lockless” methods like Interlocked.Exchange
    3. Allocate from different areas in each thread. For example by having a separate Gen0 heap per thread.
    • 0