| Author |
 Topic  |
|
|
mparker
Junior Member
USA
14 Posts |
 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. |
|
|
feline
Whole Tomato Software
United Kingdom
19109 Posts |
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. |
zen is the art of being at one with the two'ness |
 |
|
|
feline
Whole Tomato Software
United Kingdom
19109 Posts |
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. |
zen is the art of being at one with the two'ness |
|
|
|
mparker
Junior Member
USA
14 Posts |
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
Whole Tomato Software
United Kingdom
19109 Posts |
Posted - Nov 25 2024 : 09:36:07 AM
|
Thank you for the details.
Even if there is no crash, if you keep on seeing regular pauses like this, while the IDE does not respond, this is something we should look into for you and with you.
Hard to know what is going on here without more details, but at least the event viewer information gives us a clue, which is something. |
zen is the art of being at one with the two'ness |
|
|
|
mparker
Junior Member
USA
14 Posts |
Posted - Dec 12 2024 : 1:45:30 PM
|
I hadn't seen the issue again from the day of my original post until today, but I just hit it again.
Faulting application name: devenv.exe, version: 17.12.35527.113, time stamp: 0x6747908b
Faulting module name: VA_X64.dll, version: 10.9.2537.0, time stamp: 0x671ea830
Exception code: 0xc0000005
Fault offset: 0x000000000064e191
I had just navigated to a symbol with Alt+G and then used the back button on my mouse to return to where I was. It did not return, froze for a while (30+ seconds), and then exited completely like before. This probably doesn't provide much detail, as navigating to symbols and using the forward/back buttons on my mouse is what I do for hours each day without issue. I'm not sure if there's anything useful I can provide without a reliable repro, but let me know if there is and I can do my best to get it for you. |
|
|
|
mparker
Junior Member
USA
14 Posts |
Posted - Feb 12 2025 : 2:24:10 PM
|
Hi again. I had completely not seen this issue since updating to 2547 when it came out. Another coworker was also seeing it quite a lot in 2537, and was also fixed by 2547. However, today I have had it return possibly 3 times, including twice in pretty quick succession.
Things are complicated a bit by the fact that I'm on a different PC now (running Windows 11 Enterprise 23H2, before was Windows 10), working in a .sln of UE 5.5.1 now (before was 5.4.3), and today updated to Visual Studio 17.13.0, though I saw the same crash on 17.12.4 yesterday. Everything about the symptoms and Event Viewer report are the same: I click on a symbol, VS completely hangs for maybe 30 seconds, and then exits itself with no prompt. Event viewer still says it's Exception code: 0xc0000005, though now in Faulting module name: VA_X64.dll, version: 10.9.2547.0.
Yesterday when this happened, I noticed quite a lot of VA messages in the status bar where it was doing some kind of template instantiation, sometimes with class names that seemed impossibly long. Today, I haven't noticed anything interesting in the status bar. I suspect none of this will be particularly helpful in finding the issue, but it's pretty debilitating to my work, so I hope there's anything to be done about it. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19109 Posts |
Posted - Feb 13 2025 : 09:19:27 AM
|
Apologies for this, clearly the crashes aren't supposed to happen.
Can you please try following the steps here, near the button, under "Windows Error Reporting"
https://www.wholetomato.com/kb/s/save-a-minidump-file
hopefully this will get Windows to capture a dump file of the crash when it next happens. Any dump file may contain some details of the code you are working on when the crash happens, but we would only be interested in trying to work out what caused the crash, and what we can do about it. But if you are able to share any dump files from this crash, we would be most interested in having a look at them.
The best way to get them to me is to upload them somewhere, since they are often quite large, and then email me the links at:
[email protected]
including this thread ID or URL in the description, so we can match it up. This way nothing gets posted here you don't want to share with the world.
A random thought, have you enabled VA logging on your system?
We have only just discovered there is a crashing bug in our logging, yes, that is both ironic and irritating, and are working on a fix for this problem. But if you have turned On logging, as a reaction to seeing problems, this could actually make things worse, due to running into a second, separate problem. It's unlikely, but certainly not impossible, so worth asking just in case. |
zen is the art of being at one with the two'ness |
|
|
|
mparker
Junior Member
USA
14 Posts |
Posted - Feb 18 2025 : 1:11:16 PM
|
I tried last week to run my main instance of VS with another instance attached to catch the crash, but this of course prevented it from crashing. :) And it made my remote desktop software behave weirdly, maybe something to do with the live XAML debugging. I may try some of the other methods on that page this week, it will depend on when I have time.
In the meantime, I can confirm logging is not enabled, nor do I think I have ever enabled it in the past. |
|
|
|
feline
Whole Tomato Software
United Kingdom
19109 Posts |
Posted - Feb 19 2025 : 08:59:04 AM
|
Thank you for trying that. I am not sure why attaching another devenv.exe to catch any crash would stop the crash, but without knowing anything about the nature of the crash, who can say. It would have been nice if this was a problem free way of "fixing" the crash.
No logging is good. Logging turns its self off automatically, so it should not be on, but while you are seeing crashes, and its a known trigger, its best to double check. |
zen is the art of being at one with the two'ness |
|
|
|
mparker
Junior Member
USA
14 Posts |
Posted - Feb 19 2025 : 12:15:32 PM
|
I suppose it is worth mentioning that I worked the full day yesterday (18th) without issues. When I had posted on the 12th, the crashes were in quick enough succession that I disabled VA to be able to get back into VS. After re-enabling on the 13th to try and catch the crash and failing, my next day using it was the 18th, and it has still been fine. All to say... I don't know if it's some issue with the state of the symbol database at the time the crashes start, or some problem with the specific set of files I have open at the time, or what. A full day of work in VS doing the kinds of things I'm always doing doesn't guarantee a crash.
While writing this, I realized that the original post was the day I updated to VS 17.12.1, and my latest post was the day I updated to 17.13.0. The one in the middle doesn't line up with a VS version, but I'm still wondering if the crash is related to times when a full database parse is being done. It's a UE5 sln with Index Unreal Engine plugins set to All. Maybe it could be reproduced on your end with that setting if you force a DB refresh and attempt to navigate around as it's doing the parse (maybe including some Unreal C# files in your navigation, as I'm often looking at those too). I could try the same thing on my end, but I hesitate to volunteer to do something I won't like the results of. :) |
|
|
|
feline
Whole Tomato Software
United Kingdom
19109 Posts |
Posted - Feb 19 2025 : 12:28:56 PM
|
If VA detects that there was a crash the last time you used Visual Studio, it should always do a full symbol database rebuild, since we cannot assume that the database is in a valid state if the IDE didn't exit cleanly. So in theory there should not be any lingering VA symbol database problems.
That assumes that there is nothing going on that is causing a new problem when you load the IDE, of course. And also has no effect on the IDE intellisense database, but it seems unlikely, although not impossible, that there is a crash problem there.
It's possible an IDE update will have helped fix the problem, depending on what was going on. Certainly a bigger update, like moving to 17.13.0 should have a bigger impact on the IDE state and install.
I am currently working on some UE 5 tests here, for another problem report, and will keep an eye out. But we have quite a few users who work with UE, so it seems unlikely the crash is directly related to Unreal Engine, thankfully, since we would be getting far more reports. Unfortunately none of this really helps you or your situation at all.
As I am sure you know, random problems are always a pain to try and pin down. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
|
|
Crash in VS 17.12.1 with VAX 2537/2024.8
