| T O P I C R E V I E W |
| Jaskot |
Posted - May 10 2019 : 4:57:53 PM
It usually happens within 20 minutes of writing code. It can be any action that triggers it. Typing, clicking on something etc. It freezes for a good minute or so and then restarts Visual Studio, and then re-indexes the entire project.
Using Visual Studio 2019 Community 16.0.3
License: trial
VA_X.dll file version 10.9.2324.0 built 2019.03.08
DevEnv.exe version 16.0.28803.352 Community
msenv.dll version 16.0.28803.197
Comctl32.dll version 6.10.17134.706
Windows 10 10.0 1803 Build 17134.706
12 processors (x86-64, WOW64)
Language info: 1252, 0x409
|
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - May 11 2019 : 09:06:04 AM
Unfortunately here 64gb of RAM isn't as helpful as you would like, since the IDE its self is a 32bit process, so it only has access to a maximum of 4gb of RAM, which is more like 3gb in reality. |
| ChrisG |
Posted - May 10 2019 : 8:02:03 PM
I thought that might be the case. No need to see a dump. Here are some tips on lowering the memory usage of VA. It might help, depending on where your memory is being used.
https://docs.wholetomato.com/default.asp?W730 |
| Jaskot |
Posted - May 10 2019 : 7:22:43 PM
It's crashing due to it being out of memory it would seem. At the time of crashing it was using 2888mb of ram. I watched it, it was at 1300mb usage, then I created a file for an enum, started adding members and it jumped an entire gigabyte up to 2300. I'm not sure what the culprit is at this point, but I'll do more research.
I have 64gb of ram, so I know for certain it's not my machine that's out of memory. I know there's a managed process limitation, guess that's what's going on. |
| Jaskot |
Posted - May 10 2019 : 6:44:09 PM
It's very odd, it's not crashing while being debugged for some reason.. |
| ChrisG |
Posted - May 10 2019 : 5:21:28 PM
I'm sorry to hear that. Would you mind capturing a dump and sending that in to support?
You can configure Windows to capture dumps of Visual Studio automatically on crash. The details are below, under "Windows Error Reporting".
https://docs.wholetomato.com/default.asp?W303
Re-indexing is normal after a crash as the database can be left in a corrupted state. Re-indexing after a crash can be disabled, but that's not the real issue here. |
