@kevingosse.net and @chrisnas.bsky.social In the book, "Listing 4-49", seems to refer on the NonGC heap as Frozen Segment. - ThreadSky

About ThreadSky

ladeak.net • 10 days ago

@kevingosse.net and @chrisnas.bsky.social In the book, "Listing 4-49", seems to refer on the NonGC heap as Frozen Segment.

Comments

ladeak.net•5 days ago

On Page 259, there is a sentence: "The regions are initially
grouped by king: POH regions appear first, followed by gen2, gen1, gen0 regions"

I suppose king is a typo for kind.😅

kevingosse.net•10 days ago

Yes, they're the same thing 😉 Frozen segments were renamed into NonGC heap

https://github.com/dotnet/runtime/blob/main/docs/design/features/NonGC-Heap.md

ladeak.net•10 days ago

And for static types that can be allocated on a NonGC heap, the same limit of ~64KB applies as also applied for the interned strings. So it is a limitation on the NonGC heap, right?

kevingosse.net•9 days ago

I believe this is a limitation of the FrozenObjectHeapManager (used by the runtime to allocate in frozen segments) rather than the NonGC heap itself. I looked at the comment in https://github.com/dotnet/runtime/pull/49576 and it really seems like the only explanation is "it's an optimization so let's not bother"

kevingosse.net•9 days ago

If you allocate your own frozen segments (see https://minidump.net/exploring-frozen-segments/), I'm fairly sure you can store objects of any arbitrary size.

ladeak.net•9 days ago

Wait but the book also said for interned strings it is 64K, page 186: "If the size of the literal string is
larger than 64 KB, it won’t fit into the NonGC heap"

kevingosse.net•9 days ago

Yeah the wording is unfortunate. It's not that it won't fit, but rather that the allocator used internally by the runtime has this arbitrary limitation.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply