| T O P I C R E V I E W |
| kwilliams |
Posted - Feb 14 2018 : 12:29:47 PM
I recently update VA to build 2248. Now Goto fails to respond about half of the time. Has anyone else seen this? |
| 10 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Feb 23 2018 : 1:49:57 PM
Thank you for the update, if it was indeed the Windows Fall Creators Update problem, then I am fairly confident this is now fixed, since we have had several users who have tested the updates, and all report that everything now works correctly.
Obviously if this comes back again, the more information you can tell me about what is going wrong the better. |
| Tamas |
Posted - Feb 23 2018 : 11:45:14 AM
OK, I think (quietly optimistic) the solution has been found!
It was indeed the creators update. Since I'm in a large(r) organization and I use multiple PCs, IT has rolled out updates differently to the ones I use. I was able to force some updates on this office PC which did not install autimagically...
I've realised how much I depend on VAX ;) I don't envy your support teams with such an intricate dependencies on MS updates and even IT schedules running them.
Thanks for the quick feedback!
|
| feline |
Posted - Feb 23 2018 : 11:30:57 AM
I have just checked, and unfortunately the Windows 10 build number does not tell us just how up to date you are with Windows Updates.
My first thought about the blank area in the VA options dialog is the Windows Fall Creators Update problem. If you are having this problem, sometimes you should see a blank area at the top of a newly opened code file in the IDE, where the VA context and definition fields should be displayed. This is also where the Alt-m menu is shown. The problem was caused by creating windows failing, which might also explain the alt-g problem. However, on a fully patched system this problem has been fixed.
Have you ever seen any sign of blank areas like this at the top of a newly opened code file?
If not, can you please look in Windows Task Manager and see how much memory devenv.exe is using?
Also, 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? |
| Tamas |
Posted - Feb 23 2018 : 10:56:35 AM
Here is the About dialog data(shows a blank screen, but Copy produced this result):
License: xxxx@zzzz (120-user license) Support ends 2019.02.06
VA_X.dll file version 10.9.2258.0 built 2018.02.20
DevEnv.exe version 14.0.25420.1 Professional
msenv.dll version 14.0.25431.1
Comctl32.dll version 6.10.16299.19
Windows 10 10.0 Build 16299
8 processors (x86-64, WOW64)
Language info: 1252, 0x809 |
| feline |
Posted - Feb 23 2018 : 08:51:34 AM
Which IDE and OS are you using?
If you are using Windows 10, do you have all of the updates installed? There was a problem with the Windows 10 Fall Creators Update when it was first released, but the updates released since then should have helped to fix this.
Were you able to capture a mini dump of this crash?
We need to try and get your system to be stable first, then we can start looking into the Alt-g problem, and files not being scanned. |
| Tamas |
Posted - Feb 23 2018 : 06:07:22 AM
VA Options -> Performance -> Rebuild
VS2015 just crashed when trying to get here by selecting VA Options ... |
| Tamas |
Posted - Feb 23 2018 : 06:02:16 AM
I have the same problem :/
It seems that many files in the large solution(100 projects) seem to be invisible/unparsed to VAX.
1. Alt G i snot even availeble
2. It does nothing, moves the cursor down a line(??) (selecting from VA menu to be sure)
This is one of the most used functions of VAX, so its a major problem not working.
|
| feline |
Posted - Feb 14 2018 : 5:40:05 PM
Also, when you are having this problem, if you place the caret into the problem symbol, what, if anything, is shown in VA's context and definition fields? These are normally shown at the top of the editor window. |
| accord |
Posted - Feb 14 2018 : 2:15:37 PM
Also, what version of Visual Studio are you using?
You may want to try rebuilding your symbol databases to see if it helps:
VA Options -> Performance -> Rebuild |
| accord |
Posted - Feb 14 2018 : 2:14:03 PM
How are you triggering Goto? Are you using Alt+G or are you clicking on the green Go icon in the top-right corner of the editor?
When it fails, what happens?
1. nothing
2. you hear a ding sound
3. you get an error message? |
