Valgrind with GDB doesn't start correctly

1. Valgrind memory analyzer with GDB started for manual_test_debugger_gui

Behavior:

        GDB shows the error " Unexpected run control state RunControlState::Running when worker DebuggerRunTool started." and doesn't start debugging.

        After few pressings "Run" it starts.

Expected behavior:

        Analyzer and GDB starts without errors
valgrind_with_gdb.mp4

Log from qtcreator terminal: 
UNEXPECTED STATE: EngineSetupRequested WANTED: InferiorStopOk IN /home/qt/work/build/qt-creator/src/plugins/debugger/gdb/gdbengine.cpp:1247
UNEXPECTED STATE: EngineSetupRequested WANTED: InferiorStopOk IN /home/qt/work/build/qt-creator/src/plugins/debugger/gdb/gdbengine.cpp:1259
UNEXPECTED STATE: EngineSetupRequested WANTED: InferiorStopOk IN /home/qt/work/build/qt-creator/src/plugins/debugger/gdb/gdbengine.cpp:1332

Application output:
15:15:31: Debugging /home/artem/work/qt-creator-local/qt-creator/tests/manual/debugger/build-gui-Qt_6_3_0_GCC_64bit-Debug/manual_test_debugger_gui ...
==53300== (action at startup) vgdb me ...
==53300==
==53300== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==53300== /path/to/gdb /home/artem/work/qt-creator-local/qt-creator/tests/manual/debugger/build-gui-Qt_6_3_0_GCC_64bit-Debug/manual_test_debugger_gui
==53300== and then give GDB the following command
==53300== target remote | /usr/bin/vgdb --pid=53300
==53300== --pid is optional if only one valgrind process is running
==53300==
remote target does not support file transfer, attempting to access files from local filesystem.
15:15:32: Unexpected run control state RunControlState::Running when worker DebuggerRunTool started.
pid= 53300
==53300== (action on error) vgdb me ...
==53300== Continuing ...
==53300== (action on error) vgdb me ...
==53300== Continuing ...
==53300== (action on error) vgdb me ...
==53300== Continuing ...
==53300== (action on error) vgdb me ...
==53300== Continuing ...
==53300== Gdb request to kill this process