How does QProcess manages the resources when started?

Context

I'm trying to implement a sort-of orchestrator pattern for our applications.

Basically, we have three different and independent applications developped in Qt that communicate with each other using Web Socket. We'll call them "core", "business" and "ui". This is a flexibility aim as we can simply develop a new application in a more suiting technology and connect it to the others via the same communication protocole.

Now the idea is to have a simple launcher that allows us to specify which part to start. We launch this "orchestrator-like" application and it starts all required processes from a configuration file.

Everything is done in Qt currently (QML for the UI interfaces).

---

Initial Issue

I've made a custom class oriented towards reading the configuration file, preparing the processes, and starting them with their respective arguments.

This uses a std:: map of QProcess related to their name in the configuration file and launch them using QProcess:: start (<process_path>) method.

The catch is that everything went smoothly until recently. The sub processes are started and runs perfectly ; everything goes on as normal until we reach some point were the "ui" part crashes (usually an LLVM memory error or vector:: length error).

At first we thought about a memory leak or a code error but after much debugging we found that the application had no error whatsoever when we ran each part individually (without using the custom orchestrator class).

---

Question / Concerns

So, our question is: could it be that the QProcess: start() method actually shares the same stack with its parent? Three processes having the same parent, it would not be surprising than a vector of ~500 elements stored in each application can exceed the stack size when returned.