| Author |
 Topic  |
|
|
aaroneady
New Member
6 Posts |
 Posted - May 02 2025 : 12:59:57 PM
|
License: Concurrent / Superkey () Support ends 2026.04.01
VA_X64.dll file version 10.9.2556.0 built 2025.04.07
DevEnv.exe version 17.13.35931.197 Professional
msenv.dll version 17.0.35919.92
Comctl32.dll version 6.10.19041.4355
Windows 10 10.0 22H2 Build 19045.5737 (remote)
64 processors (x86-64)
Language info: 1252, 0x409
1. When opening my company's very large UE sln, VS can crash multiple times until I either disable VAX or open VS without code and then open the sln from inside of VS.
2. Right-clicking a UE macro to do the quick include adding, it can cause VS to freeze and need to be shutdown manually to continue.
What logs can I give you to help figure out why VS is crashing constantly? |
Edited by - aaroneady on May 02 2025 1:00:21 PM |
|
|
feline
Whole Tomato Software
United Kingdom
19179 Posts |
Posted - May 06 2025 : 08:23:55 AM
|
First a "random" question, how much RAM do you have on your machine? I recently ran into a problem where Visual Studio 2022 kept on crashing while trying to build the Unreal Engine source code. In the end the fix I found was to increase the amount of RAM on the machine in question. So I am wondering if you could be running into a similar issue. Hopefully not, but asking just in case.
For the crashes, would it be possible to get a dump file of the crash? If you are not sure how to do so, this page explains how:
https://www.wholetomato.com/en/kb/s/save-a-minidump-file
Please be aware that the dump file can contain some details of your solution, but we would only be interested in looking at the dump file to try and work out the cause of the crash. If this is an option, can you upload the files somewhere and let me know where to download them from? This might be best done by email, to avoid posting the details here.
Please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up.
For the right clicking on a macro problem, when you see this, is VA still parsing, or has VA finished parsing? VA automatically rebuilds its symbol database after a crash, so you are going to be seeing a lot more parsing than you should be. There will be status bar messages, and a lack of VA syntax highlighting while VA is still parsing. This should not crash either way, but its somewhere to start.
Do you get a right click menu? Or does the problem happen even before you get a right click menu?
What happens if you use ALT-SHIFT-Q or mouse middle click instead of right click? I am wondering if the right click menu is somehow an issue. |
zen is the art of being at one with the two'ness |
 |
|
|
aaroneady
New Member
6 Posts |
Posted - May 14 2025 : 5:24:49 PM
|
quote:
Originally posted by feline
First a "random" question, how much RAM do you have on your machine? I recently ran into a problem where Visual Studio 2022 kept on crashing while trying to build the Unreal Engine source code. In the end the fix I found was to increase the amount of RAM on the machine in question. So I am wondering if you could be running into a similar issue. Hopefully not, but asking just in case.
I definitely have enough RAM, 256GB.
I'll talk to my IT department about the dump file. Perhaps we have a Whole Tomato contact for my company.
quote:
Originally posted by feline
For the right clicking on a macro problem, when you see this, is VA still parsing, or has VA finished parsing? VA automatically rebuilds its symbol database after a crash, so you are going to be seeing a lot more parsing than you should be. There will be status bar messages, and a lack of VA syntax highlighting while VA is still parsing. This should not crash either way, but its somewhere to start.
Do you get a right click menu? Or does the problem happen even before you get a right click menu?
What happens if you use ALT-SHIFT-Q or mouse middle click instead of right click? I am wondering if the right click menu is somehow an issue.
This one doesn't happen often but if I see it again I'll pay attention to these details. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19179 Posts |
Posted - May 15 2025 : 07:42:05 AM
|
Thank you for confirming that. The amount of RAM never seemed like a good theory, but worth asking since it was something I had recently run into myself.
We would only be interested in using a dump file to try and diagnose the problem, but once sensitive information is involved, we all have to be careful!
If this is happening really quite often, it might be worth installing VA into a new test profile, and using the test profile for a few hours. This will tell us if the problem is somehow profile specific. This can happen if there is an interaction problem between VA and another installed extension, or even a corruption problem in the default profile.
If you want to try this, can you first download the VS2022 specific installer for Visual Assist from:
https://downloadfiles.idera.com/WholeTomato/VA_X_Setup2556_0_x64.vsix
Next you will need extra details about the IDE install to create a test profile. To get these details, please open a Windows command prompt window, and inside the window run the command:
"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe"
There will be a set of lines for each different version of Visual Studio that you have installed. For the version you want to install into, you want the "productPath", "dispalyName" and "installationVersion" lines, e.g.
productPath: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
displayName: Visual Studio Professional 2022
installationVersion: 17.13.35931.197
You can then use the information from these three lines to make sure that the following command has the correct command line parameters. The values are:
/appidname: = displayName:
/appidinstallpath: = productPath:
/skuVersion: = installationVersion:
The "/skuName:" value is one of "Community / Pro / Enterprise", note for the Professional version it is "Pro", not the expected "Professional".
The working command, for VS2022, using the values above, is - split into lines to make it easier to read and edit:
"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\VSIXInstaller.exe"
/appidinstallpath:"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe"
/skuName:Pro
/appidname:"Visual Studio Professional 2022"
/skuVersion:17.13.35931.197
/rootSuffix:"VATest" "C:\Users\%USERNAME%\Downloads\VA_X_Setup2556_0_x64.vsix"
The "rootSuffix" is the name of the test profile you want to install to, and this will be created if it does not already exist. The final parameter is the path of the VSIX installer for Visual Assist that you want to install. Once you have the command set up, the only parts you should need to edit are the skuVersion and the path to the VSIX file, can you please close all instances of Visual Studio and run this command.
Running this command installs VA into the test profile, but it does not load the test profile. If you created the test profile by installing VA, when you run the test profile it will be using the default IDE settings, without asking you which settings you want to use.
To now load the test profile you use the command:
"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest
To load your normal, default profile just load the IDE normally. To return to this test profile again, pass the /RootSuffix command line switch when loading the IDE. You can run both profiles at the same time, next to each other. In VS2019 and VS2022 the profile name will be shown just under the close button, in the top right hand corner of the main IDE window. If you export your IDE settings from your main profile you can them import them into the test profile.
|
zen is the art of being at one with the two'ness |
|
|
|
aaroneady
New Member
6 Posts |
Posted - May 22 2025 : 8:14:02 PM
|
Just to close this out, I figured out the issue.
I opened the Windows Event Viewer and looked at the crash event. It turned out to be the UnrealVS extension. After updating it, everything seems fine. Thanks for the assist. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19179 Posts |
Posted - May 23 2025 : 04:50:56 AM
|
Many thanks for the update, it is good to know you found and fixed the problem.
Any advice on how you worked this out from the Windows Event Viewer? I don't think I have ever looked at that, to try and work out a crash event, so I am wondering how you went about this, if you have time to offer any advice. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
|
|
VS2022 crashing in different ways
