debugger frozes debugged app GUI if AN screen reader no matter of its name is being used

[JanuszChmiel]

Yours app is excellent. Fast, you have even included Github support, you are using Scintila and GUi is very accessible. I would like to kindly debate with you as A elite Autohotkey developer about very complex programmers issue. When I debug some Autohotkey script from AHK Studio, and if this script creates GUI, which can allow not only visually impaired user to navigate around GUI focusable elements by pressing arrow keys or TAB or SHIFT+TAB, window of such GUI will be frozen totally.

As A result. Communication between screen reader process and GUi window totally stop. When screen reader user is inside such window, screen reader will stop to operate at all. No key presses are indicated by screen reader. I must restart screen reader in such situation and I must force close window with GUI of app, which I want to debug.
No matter, which screen reader I Am using. Even Narrator, screen reader made by Microsoft is being suffering because of this issue. The question is, who would have so deep C++ language knowledge, patience and good will to try to find The cause of this issue.
As A result, I can not work with GUI of script, which I would like to debug. Sure, I can start debugging, but even AHK window frozes immediately, when I run debug command.

I have spent some time to try to use various debuggers, but there is The same problem.
I can only use variable Wars or similar script from The core developer of Autohotkey, who is making complex changes inside Autohotkey C++ source code on Github. Any advice how to constructively help to debug will be very welcomed.
Unfortunately for Me, I can not use Process monitor, because even 4 core modern laptop frozes if screen rreader try to fetch so many listwiev items inside Process monitor window. As A result, I can not navigate across Process monitor window to fetch some errors.
Thank you very much for yours advices.