If clicking Start Profile of QmlProfiler and executable is not (yet) known the profiler still seems to try to start and connect the socket which obviously fails as there is no executable started.

Trying to stop the profiler with the Stop button does not work, so I cannot get the profiler back in a working state without restarting QC.

Steps to reproduce:

• create a Qt Quick Application (compat), use Qbs as build system
• have build before run enabled (should be default)
• without explicitly building trigger start profiling

Qbs seems to update the run config too late, so on the first run the executable is empty.