|
aaroneady
New Member
4 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
19171 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 |
 |
|
VS2022 crashing in different ways
