| Author |
 Topic  |
|
|
g0dpEUmE
Junior Member
24 Posts |
 Posted - Apr 13 2026 : 12:01:02 AM
|
Windows 10, VS2010, VA2610
I seems to have found the reason for constant freezes of IDE by VA, probably it's VA's expansion of macros.
With latest VA installed VS constantly freezes, whenever scrolling, hovering over something or editing, and now I've found it on the simplest program that when I hover over a macro, or even hovering over the line that it lays, or click between whichever two characters in this line, the IDE freezes. Other tooltips like function definitions, typedefs doesn't come up with this problem. Problem persists even if I turn off the "Show quick info tooltips for more symbols" in VA config.
Recording link: https://we.tl/t-Zqkujxaok9Ud8LsN
And the tooltip can fail conditionally.
Hope these problems can be solved.
There are just many bugs to be addressed and I don't think it's right to drop Windows 7 support here... There should be other way out, maybe some options. |
Edited by - g0dpEUmE on Apr 13 2026 09:54:33 AM |
|
|
feline
Whole Tomato Software
United Kingdom
19362 Posts |
Posted - Apr 13 2026 : 11:53:15 AM
|
Which OS, version of Visual Studio and version of VA are you seeing this with?
As for Windows 7 support, is there a reason you are using such an old OS? I have VS2010 installed here under Windows 11 and it looks quite happy and content. So it is not as simple as this version of Visual Studio simply doesn't install under or run under newer versions of Windows.
A broader question is how long we should support old, no longer supported versions of Windows. That depends partly on the number of customers who report using these situations. Those resources could be focussed on fixing any issues with Visual Studio 2026 instead, or some other problem. With limited resources, which is the reality for nearly everyone, somehow you need to prioritise what to work on, and what to support. |
zen is the art of being at one with the two'ness |
 |
|
|
g0dpEUmE
Junior Member
24 Posts |
Posted - Apr 13 2026 : 6:41:56 PM
|
quote:
Originally posted by feline
Which OS, version of Visual Studio and version of VA are you seeing this with?
As for Windows 7 support, is there a reason you are using such an old OS? I have VS2010 installed here under Windows 11 and it looks quite happy and content. So it is not as simple as this version of Visual Studio simply doesn't install under or run under newer versions of Windows.
A broader question is how long we should support old, no longer supported versions of Windows. That depends partly on the number of customers who report using these situations. Those resources could be focussed on fixing any issues with Visual Studio 2026 instead, or some other problem. With limited resources, which is the reality for nearly everyone, somehow you need to prioritise what to work on, and what to support.
I've been working on VS2010. This problem is reproduced on Windows 10,VA 2610, and in fact has already been there since recent VA releases. I haven't seen this in old versions of VA.
There's a complete toolchain implemented on Windows 7 in which some of the softwares are system sensitive and even hardware sensitive, there are old workstations running there which can't be easily replaced, and the target machine of product is Windows 7 as well, so the consistency is advantageous for the development.
However it's true that resource is limited. I can't tell how much of va users are using Windows 7#65292;at least I'm one of them, and I don't know the architecture of va, but I believe there can be some ways out. I have some proposals which can be considered.
Compatible mode - newer va disables functions not compatible with older oses so only old compatible components are enabled.
Bugfix only - only bugfix patches of existing functions in old versions such as 2025.3 for old os, no new functions released.
Delayed support - releases for old oses released annually, semiannually or so.
Still thanks for support. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19362 Posts |
Posted - Apr 14 2026 : 10:44:04 AM
|
From a support point of view, so NOT a comprehensive survey, I had to re-surface a Windows 7 VM I had not touched in years recently. We are looking at 2 or 3 users in the last 2 years who have reported working on Windows 7. Approximately "everyone" who reports a problem is working in VS2022 or VS2026.
I know we make some efforts to collect more accurate details here, but from a commercial point of view, Windows 7 just isn't a consideration at the moment, unless something significant changes.
For pausing, why do you think it is macro expanding? Is this happening on mouse hover over a tooltip? Is there some pattern that makes you think this? There may be some thing we can do here if you are seeing specific problems with specific macros, depending on what the trigger / pattern is. |
zen is the art of being at one with the two'ness |
|
|
|
g0dpEUmE
Junior Member
24 Posts |
Posted - Apr 14 2026 : 10:56:26 AM
|
quote:
Originally posted by feline
From a support point of view, so NOT a comprehensive survey, I had to re-surface a Windows 7 VM I had not touched in years recently. We are looking at 2 or 3 users in the last 2 years who have reported working on Windows 7. Approximately "everyone" who reports a problem is working in VS2022 or VS2026.
I know we make some efforts to collect more accurate details here, but from a commercial point of view, Windows 7 just isn't a consideration at the moment, unless something significant changes.
For pausing, why do you think it is macro expanding? Is this happening on mouse hover over a tooltip? Is there some pattern that makes you think this? There may be some thing we can do here if you are seeing specific problems with specific macros, depending on what the trigger / pattern is.
At least it must be a major cause, the IDE almost freezes everytime when I hover over a macro for tooltip, almost all macros, just select whichever one in listbox and repeat the steps and problem will occur.
And in recent usages I find not only hovering over a macro, but also moving the cursor through the line that the macro lays, or typing in neighbouring lines. As we can see this problem is exceedingly serious. As long as there are many macros in the file then the problem is easily triggered and IDE just freezes one time after another, almost unusable.
I've tested that since some 2023 versions, at least the 2023.5 I've used, it already starts to pause ide, although not for that long at that version, for less than a second, but still frequent and experience impacting. And now it's pausing for too long. 2022.6 doesn't see this problem. While macro expansion may not have been introduced in 2023, I doubt there may be other causes. But at least at recent versions the problem is too serious, and I have to roll back for this time being. There should be an option to disable this feature. |
Edited by - g0dpEUmE on Apr 14 2026 10:07:37 PM |
|
|
|
feline
Whole Tomato Software
United Kingdom
19362 Posts |
Posted - Apr 15 2026 : 11:12:28 AM
|
OK, this is a problem description I can test.
If you make a new, default C++ solution, do you see this same pause when hovering the mouse over a macro? I am not seeing the problem here, so it isn't as simple as using VS2010 with a recent version of VA. So it could be something about your solution that is a factor.
If you see the same behaviour in a new, default solution can you please export your VA and IDE settings and send them to me:
VA Options -> Advanced -> Logging and Recovery -> Export Settings
IDE tools menu -> Import and Export Settings -> Export selected environment settings
I can then import them here and see if I can reproduce the problem. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
|
|
VA freezes the IDE probably due to macro parsing
