Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Crash in VS 17.12.1 with VAX 2537/2024.8

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
mparker Posted - Nov 21 2024 : 3:37:58 PM
I just updated to VS 17.12.1 today (11/21) from 17.12.0 around 11/14, and VAX 2024.8 two days ago (11/19), from I think 2024.6. Currently working in an Unreal project that's on 5.4.3.

This afternoon, I've had 2 crashes when looking at some C# files in Unreal (*.Build.cs files). I haven't been able to reproduce it when looking at the same files again, and I'm not sure how to get you the most useful information even if I can repro it (so please let me know). Here's the first Windows Event Viewer log.

Faulting application name: devenv.exe, version: 17.12.35514.174, time stamp: 0x67369be7
Faulting module name: VA_X64.dll, version: 10.9.2537.0, time stamp: 0x671ea830
Exception code: 0xc0000005
Fault offset: 0x00000000002548cd
Faulting process id: 0x7654
Faulting application start time: 0x01db3c43f3855894
Faulting application path: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
Faulting module path: c:\users\mparker\appdata\local\microsoft\visualstudio\17.0_9f85749b\extensions\d2ykka54.wpy\VA_X64.dll
Report Id: 984c85db-d20f-4510-935a-7b626367a600
Faulting package full name:
Faulting package-relative application ID:

The other one was 12 min later and looks much the same, except:
Fault offset: 0x000000000065688c
Faulting process id: 0x9a1c

Happy to provide more info if I encounter it again and have a way to do so, but heads up that there may be some problem in 17.12.1.
3   L A T E S T    R E P L I E S    (Newest First)
mparker Posted - Nov 22 2024 : 11:30:41 AM
The project is in UE 5.4.3. It's hard to remember exactly what I was doing, but I believe both times I was double-clicking a symbol to highlight it. The symbol is in a block that's like

#if UE_5_2_OR_LATER
foo
#else
SymbolIWasClicking = bar;
#endif

so the symbol was greyed out to Intellisense and not being compiled. I have gone back to the same file and clicked the same thing without issue, and I had a teammate try it with no issue.

The form of the crash was VS becoming completely unresponsive for ~20-30 seconds and then exiting completely. No indication as to what was happening at the time or afterwards. I only checked the Event Viewer after the second time, and found that it was a similar problem both times. No more issues since then, though I may not have been doing the same exact kind of work the rest of the day.
feline Posted - Nov 22 2024 : 07:37:23 AM
I have put in a bug report so we can keep an eye on this:

case=165200

which version or versions of Unreal Engine are you working with? I am not sure if this matters, but its another factor to check.
feline Posted - Nov 22 2024 : 07:32:41 AM
Are you getting a chance to debug this when the crash happens? I am wondering if there is any chance of a mini dump file, or even a full dump file?

Do you have any sense of the trigger? Did it seem like you were doing the same thing when the crash happened, or is there no sense of a pattern yet?

So far you are the only person reporting this, but any crashes are a serious concern, so I would like to try and pin this down if at possible.

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000