I am using uVision V5.18.0.0 running under Windows 10, building code for various STM32F parts.
My problem is that the IDE stops responding at various places for a long time, sometimes over 5 minutes, occasionally over 10, but eventually recovers.
This happens mostly at the completion of a build, occasionally on entering a debug session and occasionally when leaving a debug session.
While it isn't responding, a quick look at the Windows task manager shows the IDE is still consuming processor time, around 20%, and using a lot of memory, anything up to 2 GB!
It is becoming an issue that I have to wait for so long after running a build, and I would really appreciate a fix to this problem.
No, all local and no version control hooked into uV.
I think Andrew might be thinking of Windows Explorer (Shell) Extensions, the sort of thing Tortoise CVS/SVN do. Where as AV is probably at a filter driver level.
Another thing to watch is the generation of Browse information, this has been a complete dog in uV for years, not sure if it was written by an intern using bubblesorts, but it turns the compile exercise into one where you can go brew a pot of tea/coffee waiting for it. Feels very 1986 TBH.