A process can have several threads. Garbage collection works within one process.
On systems that support fork: If you disable the garbage collection in one process and then fork it (= create a copy of the process) then GC should also be disabled in the copy.
If new processes are created which are not a copy then they have their own garbage collection configuration. By defaut their GC should be turned on.
But there are a lot of libraries which have a Process
class. I can not tell what they do. If you use os
to spawn a new process (not a copy) then it should run with GC turned on.
The configuration of one process's GC has no effect on the configuration of an other's GC. Processes are boundaries to protect code from oneanother. So anything in one process is not able to reach into an other process, easily.