Refcount for retainHaxeObject ?

[singpolyma]

Right now there is no refcount with retainHaxeObject. That means that if two methods are called which both return the same object (or the same method twice, etc) by different parts of the C code, then one part of the C code calls release the GC may free it even though there is still a reference on the C side.

[haxiomic]

Agree and good catch
I think a simple fix could be changing the gcRetainMap from <ptr, Dynamic> to <ptr, { obj: Dynamic, refCount: Int }>

haxe-c-bridge/HaxeCBridge.hx

Line 1806 in 2ae120d

public static final gcRetainMap = new Int64Map<Dynamic>();

I'm not working on this repo at the moment but would accept patches for this