Doesn't the GC only access private fields though? So it wouldn't be a case of the GC mangling objects you are working on as that memory space isn't going to get touched.
Rather, is it GCCollect running concurrently in multiple threads that causes crashes or screwing up an objects reference count, perhaps deallocating them prematurely?
In any case I should be fine disabling automatic Garbage Collection while a thread is running, yes?
Rather, is it GCCollect running concurrently in multiple threads that causes crashes or screwing up an objects reference count, perhaps deallocating them prematurely?
In any case I should be fine disabling automatic Garbage Collection while a thread is running, yes?