GC issue? List.pool overwritten by allocated object

[Steven Schveighoffer]

On Sunday, 18 May 2025 at 15:49:21 UTC, Denis Feklushkin wrote:
> This is was wrong approach. SIGSERV caused by FINALIZE attr 
> bits on some of GC.malloc() calls without acltually specified 
> class info

Oof, yes. The gc_malloc calls with the FINALIZE bit set need 
either a class object to be filled in, or a struct finalizer 
supplied via the TypeInfo (you are not supplying any to the 
calls).

> That's it, I have no other ideas

Memory problems suck. Finding out why something did something 
after the fact is nearly impossible.

In all my experience with the GC, and I've had a lot over the 
last year, these problems are extremely difficult to find.

Please send me an email, maybe we can do some kind of session to 
try and find the problems. I have very good current knowledge of 
the GC, but I'm not going to be able to understand your program 
without help.

-Steve