Both in my application, and in the Juce demo, the performance of Juce is decreased if a debugger is attached. This is for a Release build (full optimization). This happens with both the Intel C++ compiler and the MSVC compiler.
Juce Demo draw time reports 1.09 ms when running with a debugger attached. When I run the Juce Demo stand-alone from Explorer. the draw time drops to 0.79ms.
In my own app things are far worse, when I resize my main window, and it was launched from the debugger, it looks painfully slow. But when I run standalone, it is actually fairly fast (now that I compiled with Intel C++).
Nothing is written to the Output or Debug windows.
Any ideas why this would be? It’s kind of annoying…