| T O P I C R E V I E W |
| ldrs |
Posted - Feb 11 2020 : 2:43:48 PM
VS 2019 Preview 16.5.0 Preview 2.0. VAX 10.9.2358.0 built 2019-12-19.
I had VS open and clicked the close X in the top right corner.
While closing, devenv.exe crashed with:
</StackTrace><ExceptionString>System.ExecutionEngineException: Exception of type �System.ExecutionEngineException� was thrown.</ExceptionString></Exception></TraceRecord>
An unhandled exception of type �System.ExecutionEngineException� occurred in Unknown Module.
I reported the issue in the Visual Studio community but it seems to be related to VAX:
https://developercommunity.visualstudio.com/comments/913231/view.html
According to their analysis, "we are getting an Access Violation while freeing the RCW for VaManagedComLib.IVaDebuggerToolService. You should report the problem to them (linking them here), I can chat with them or (possibly) get them the dump if they wanted to look further." |
| 15 L A T E S T R E P L I E S (Newest First) |
| sean |
Posted - Apr 09 2020 : 1:18:51 PM
I opened a bug report for Visual Studio regarding this crash:
https://developercommunity.visualstudio.com/content/problem/952829/crash-during-exit.html
They closed it as a dupe of another bug report I opened. That one is apparently fixed for the next 16.6 preview release. |
| sean |
Posted - Apr 03 2020 : 12:59:10 PM
Yes, we are experiencing similar inconsistent recurrence in 16.6 and are investigating. case=142074 |
| ldrs |
Posted - Apr 03 2020 : 12:37:04 PM
I have had another crash while closing VS just now.
VS 2019 16.6.0 Preview 2.0
VAX 10.9.2366
It might still be the same issue. It happens only sometimes, not consistently. |
| sean |
Posted - Feb 20 2020 : 10:49:39 PM
The changes that were in 2363 are now officially released in build 2366.
https://support.wholetomato.com/default.asp?W404#2366
|
| sean |
Posted - Feb 18 2020 : 7:22:52 PM
thanks for the clarification |
| ldrs |
Posted - Feb 18 2020 : 2:52:19 PM
I cannot say if it is specific to 16.5 preview 2 only. It might be but I am not certain. I've mostly been using the preview version and don't remember exactly when the crashes started. |
| sean |
Posted - Feb 18 2020 : 2:39:46 PM
the thing I'm trying to determine is if the behavior changed specifically in vs2019 16.5 preview 2, or did the same crashes happen in vs2019 16.0, 16.1, 16.2, 16.3, or 16.4?
in other words, did the crashes only start after moving to 16.5 preview 2?
I'm specifically asking about VS 2019 -- not any other VS like 2017 or 2015. |
| ldrs |
Posted - Feb 18 2020 : 2:29:16 PM
I have used all previous version of VS: 2003, 2005, 2008, 2010, 2013, 2015, 2017, 2019. |
| sean |
Posted - Feb 18 2020 : 11:17:10 AM
Have you used earlier versions of VS2019, or is 16.5 preview 2 the first version of VS2019 that you have used? |
| ldrs |
Posted - Feb 18 2020 : 02:11:18 AM
No, it only happened in VS2019. |
| sean |
Posted - Feb 17 2020 : 7:36:24 PM
Do you recall ever having experienced the crash in earlier versions of VS2019? |
| ldrs |
Posted - Feb 12 2020 : 3:29:54 PM
There are 70 projects and VA's Open File in Solution dialog shows [2134 of 2134].
I did not have the crash with debugger integration disabled yet. I am going to re-enable it and try with 2363_0. |
| feline |
Posted - Feb 12 2020 : 08:19:12 AM
How large is your solution? As a way to measure this, how many files do you have in your solution?
If you open VA's Open File in Solution dialog (Alt-Shift-O) the title bar contains two numbers. The first number is the number of files currently listed, which changes as you filter the list. The second number is the total number of files in the list, which is normally the number of files in your solution. What is this second number?
It is possible that solution size is a factor here, but I am not sure why it should be. |
| ldrs |
Posted - Feb 11 2020 : 3:30:42 PM
It's not consistently reproducible; happens every couple of times. I always have a larger solution open before closing VS.
Debugger integration is turned on. I can try turning it off but it will take a while to see if it crashes again. |
| feline |
Posted - Feb 11 2020 : 2:59:10 PM
Was this a one off problem, or are you seeing this every time you close VS2019 preview?
I am assuming you have:
VA Options -> Debug Assistance -> Enable debugger integration required by VA Step Filter for native C/C++
turned On. Assuming you are able to load and exit the IDE without a crash can you try turning this setting off and see if it makes any difference? I will install this preview here and see if I can reproduce this problem. |
