C struct garbage collection not run frequently enough

[Sukera]

@vchuravy

The Boolean being passed decided between a incremental or full collection:

Ah right, mixed it up with GC.enable

@mattsignorelli

This is interesting. The library uses its own special allocator instead of malloc by default (uses a thread-safe pool of memory), but I’d like to try jl_malloc since it actually might be faster in this case

If the library doesn’t provide a way to use a custom malloc, it’ll be difficult to just drop jl_malloc in there.

---

One thing I’m wondering about, looking at the struct definition, is why you’re wrapping a pointer? Ordinarily, I’d make the RTPSA struct mutable (to communicate to julia that it has a stable address) and just use that directly, perhaps attaching the finalizer there, retrieving the object pointer through pointer_from_objref (which should be safe here, since the object is alive in the finalizer). Why the additional indirection?