From Sentry: https://the-qt-company-00.sentry.io/share/issue/ee3af70d1eff4a9c8ec32f168831917c/

From what I can tell, the setupDevicesWatcher can lead to a stack overflow:

The call to "handleDevicesListChange" will trigger a call to "emulatorName()" which will start a Process::runBlocking, which can in turn trigger the "readyRead" signal of the device watcher process again (and again, and again).

While this is not an endless loop, the deep stack seems to be able to grow beyond the available stack size. Probably a delayed "handleDevicesListChange" would work around this problem.