GC issue? List.pool overwritten by allocated object

[Denis Feklushkin]

On Monday, 12 May 2025 at 21:29:10 UTC, Steven Schveighoffer 
wrote:

>> Yes, of course I understand perfectly well. And it seems to me 
>> that I am not doing anything "reprehensible".
>
> The "reprehensible" thing that almost always causes GC issues 
> is use after free because you are interacting with C memory.

I just added `GC.collect()` before lines what caused SIGSERV and 
all was fixed. Is that what you meant?

If so, I don't understand the nature of this error

I feel uncomfortable about all this: if it fixes problem - then 
why? If it doesn't, then there must be a bug somewhere that is 
causing and collect() jsut masks it

[Commit](https://github.com/denizzzka/pukan/commit/a60d0487ba8c2a4ec5a7fd8394fc5cd01753e17b) that fixes(or not?) issue