Is this crash something you can reproduce in a deterministic way?
From the callstack I see it happens when destroying a page containing a ListBox with tooltips, I don't know if that points to any known screen.
It would help to have a way to reproduce it and narrow the xaml causing it.

I may have an idea on what could be happening, I generated a new library with a possible fix, could you please give it a try?

https://drive.google.com/file/d/1S7Wo3daVvzo_7c0gFOKJTzbPSBFNQpoK

I'll try the fix now, thanks.

I've attached the XAML files for the screen which leads to the problem.

Thanks for the xamls.

I think I was too fast on providing the fix, it won't solve it. But I'm pretty sure where the problem comes from.
I need a bit more time to figure out the correct way to fix it.

You are correct, the fix didn't work.

I appreciate your attention, thanks! :)

Finally I was able to reproduce the issue, could you please try the following fix in your game. In NoesisGUI/Plugins/API/Proxies/PropertyMetadataExtend.cs line 184 instead of just returning IntPtr.Zero:

BaseComponent.AddReference(baseValue); // released by native bindings

return baseValue;

This should fix it.

This fixed the issue, thank you!