C struct garbage collection not run frequently enough

[Sukera]

@mattsignorelli

The C code constructor spits out a pointer to the struct that the C allocated (not Julia)

It doesn’t matter to unsafe_load who allocated the memory behind the pointer. It simply loads the value behind the pointer, i.e. it dereferences the pointer.

@mattsignorelli

So given some Ptr{RTPSA}, how exactly do I construct a new Julia RTPSA object?

You don’t construct anything; unsafe_load gives you the object at the address of that pointer. The object already exists right there. Does the object not exist at that address?

@mattsignorelli

e.g. I modified the code to make RTPSA mutable. I can’t just return unsafe_load because now that allocates a new object:

@mattsignorelli

julia> @allocations unsafe_load(tpsa)
1

I am pretty sure that this is an artifact of accessing the non-const global tpsa. The allocation should be from the resulting dynamic dispatch.