| T O P I C R E V I E W |
| BobClarke |
Posted - Dec 12 2017 : 3:02:18 PM
I updated VS2017 to 15.5.1 a few days ago, and since then, I have been often seeing the dialog about an exception occurring that "may be caused by an extension." Since Visual Assist is the only extension I have enabled, other than the ones Microsoft makes you keep if you want to do C++ development (Roslyn stuff and VS Extensions for JavaScript), I suspect VA is the cause, but I don't know for sure.
Here is the VS log file about the error:
System.NullReferenceException: Object reference not set to an instance of an object.#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Operations.Implementation.CodeStructureNavigatorProvider.<
>
c__DisplayClass14_0.<
GetBracePairsForContentType>
b__0(BracePair pair)#x000D;
#x000A;
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()#x000D;
#x000A;
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source)#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Operations.Implementation.CodeStructureNavigatorProvider.GetBracePairsForContentType(IContentType contentType)#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Operations.Implementation.CodeStructureNavigatorProvider.CreateTextStructureNavigatorInternal(ITextBuffer textBuffer)#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Operations.Implementation.CodeStructureNavigatorProvider.<
>
c__DisplayClass10_0.<
CreateTextStructureNavigator>
b__0()#x000D;
#x000A;
at Microsoft.VisualStudio.Utilities.PropertyCollection.GetOrCreateSingletonProperty[T](Object key, Func`1 creator)#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Operations.Implementation.CodeStructureNavigatorProvider.CreateTextStructureNavigator(ITextBuffer textBuffer)#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Operations.Implementation.TextStructureNavigatorSelectorService.<
>
c__DisplayClass14_0.<
CreateNavigator>
b__0(ITextStructureNavigatorProvider provider)#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.<
>
c__DisplayClass17_0`3.<
InvokeBestMatchingFactory>
b__0()#x000D;
#x000A;
at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.CallExtensionPoint(Object errorSource, Action call)#x000D;
#x000A;
--- End of stack trace from previous location where exception was thrown ---#x000D;
#x000A;
at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)</description>
</entry>
License: [email protected] (1-user license) Support ends 2018.12.13
VA_X.dll file version 10.9.2238.2 built 2017.11.10
DevEnv.exe version 15.0.27130.2003 Professional
msenv.dll version 15.0.27130.2003
Comctl32.dll version 6.10.15063.0
Windows 10 10.0 Build 15063
8 processors (x86-64, WOW64)
Language info: 1252, 0x409
Platform: Project defined
Stable Includes:
C:\Dev\vcpkg\installed\x64-windows\include;
C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.2.0\Source;
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.7\Include\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\um;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\UnitTest\include;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\include;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\atlmfc\include;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\include;
Other Includes:
Stable Source Directories:
C:\Program Files (x86)\Codejock Software\MFC\Xtreme ToolkitPro v18.2.0\Source;
C:\Program Files (x86)\Windows Kits\10\Source\10.0.15063.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\src;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\crt\src;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\atlmfc\src\atl;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\atlmfc\src\mfcm;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\atlmfc\src\mfc;
*************
Am I on the right track, or does VA have nothing to do with this?
Bob
|
| 15 L A T E S T R E P L I E S (Newest First) |
| sean |
Posted - Dec 18 2017 : 7:21:31 PM
case=112698 was opened for the Code Inspection crash that started with the 15.5 update.
case=112698 is fixed in build 2248. |
| feline |
Posted - Dec 15 2017 : 05:07:06 AM
I hate random problems like this. It's nice when they go away, but very unhelpful when they occur often enough to be an issue, but rarely enough to be hard to pin down. We will work with you to try and pin this down, but being able to reproduce this on demand would make things a lot easier for all of us  |
| BobClarke |
Posted - Dec 14 2017 : 2:02:13 PM
@feline: If I can reproduce it, I'll try that. But the error has only occurred once this morning, and when I followed the same steps to try to reproduce it, nothing happened.
I'll keep experimenting. |
| feline |
Posted - Dec 14 2017 : 12:27:39 PM
If you have the time, can you please try this test. First close all instances of VS2017, then run the command:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest
this will load VS2017 with a new, default profile, including the default set of extensions. Normally useful for testing your extensions, but since everything looks normal here, this will also allow us to check for something odd with your IDE / VA settings, or your default profile. You will need to install VA by going into the:
IDE tools menu -> Extensions and Updates...
dialog, and searching online for VA.
If you load VS2017 normally, without this command line switch, then you will get your normal profile and settings, so nothing is lost. But if this exception is happening fairly often, this is a way to narrow down the conditions under which it happens. I have seen a couple of cases where a strange problem is specific to the default profile, even though we were never able to find the actual problem. |
| sean |
Posted - Dec 14 2017 : 12:24:26 PM
The log doesn't appear to have recorded dlls of the functions in the callstack. If you are able to repro, you could attach a second instance of VS to the first and configure the debugger to stop on System.NullReferenceException. Then you would be able to see the dlls in the callstack. System.NullReferenceException might be normally thrown and handled during normal operations, so it might be too noisy to enable the stop on that exception without a way to repro. Seeing the dlls might lead to a smoking gun. |
| BobClarke |
Posted - Dec 14 2017 : 12:18:51 PM
@Sean: It's not a crash, so there is no dump file. Visual Studio writes the error info to an XML file called ActivityLog.xml in this folder: C:\Users\Optio\AppData\Roaming\Microsoft\VisualStudio\15.0_b4eff186.
That's what I posted in my initial post. I'm still not convinced that it is a problem with Visual Assist.
|
| sean |
Posted - Dec 14 2017 : 12:01:56 PM
Are you able to save a minidump of the crash? If so, zip it up and upload it at https://www.wholetomato.com/support/contact.asp
Details here: https://support.wholetomato.com/default.asp?W303 |
| BobClarke |
Posted - Dec 14 2017 : 12:00:18 PM
@Sean: I guess I spoke too soon. It just happened again, when I started a C++ debugging session. |
| sean |
Posted - Dec 14 2017 : 10:43:42 AM
@BobClarke interesting, thanks for the update. |
| BobClarke |
Posted - Dec 14 2017 : 09:42:59 AM
@Sean: The only other enabled extensions I have installed are the ones I cannot remove without also disabling C++ development. And I noticed the "date installed" changed to 12/12/2017 for the Roslyn extensions, and I didn't make any changes, so I assume they were automatically updated by Microsoft. One or more of those extensions may have been the source of the problem because the error has not occurred in the past couple days.
|
| Thomas Wollenzin |
Posted - Dec 14 2017 : 03:48:12 AM
Thank you Sean, looking forward to it! |
| sean |
Posted - Dec 13 2017 : 10:28:22 AM
@Thomas Wollenzin
VS2017 15.5 introduced some header changes that crash the Code Inspection parser. To prevent that particular crash, disable Code Inspection. A fix will be available at the end of the week.
@BobClarke
We don't have any symbols that contain the text "DisplayClass" -- do you have any other third party extensions installed? |
| Thomas Wollenzin |
Posted - Dec 13 2017 : 04:41:47 AM
I am seeing a similar issue.
VS2017 IDE is crashing whenever I save a change.
With VA extension disabled the instabilities are completely gone.
VS2017 is at 15.5.1 and I also installed latest Microsoft Win10 x64 updates.
The VS2017 log file contains numerous entries of this format.
<entry>
<record>836</record>
<time>2017/12/13 09:24:53.291</time>
<type>Information</type>
<source>ExtensionCrashNotification</source>
<description>C:\USERS\THOMASW\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\15.0_C7DD9675\EXTENSIONS\XXEKO2G2.ZXV\valibclang.dll!clang_index_setClientEntity</description>
</entry>
|
| BobClarke |
Posted - Dec 12 2017 : 4:20:36 PM
I am not using a .editorconfig file.
The error message occurs most often when I am opening a solution from the taskbar by right-clicking my VS2017 icon and loading the solution. Just before the editor window, Solution Explorer and other windows appear, the error dialog appears.
But I have not been able to repeatedly reproduce it, so I'll keep trying.
|
| feline |
Posted - Dec 12 2017 : 3:58:35 PM
Are you using a ".editorconfig" file with your solution? There is a known problem where there can be a hang in VS2017 with VA and a .editorconfig file, which might explain what you are seeing here.
Are you seeing any pattern to when this dialog appears? Opening a file? Editing a file? Closing a file? Compiling?
If you go into the:
IDE tools menu -> Extensions and Updates...
dialog and Disable VA in the list of installed extensions, and then restart the IDE, does this have any effect? If this fixes the problem its safe to say VA is somehow involved. |
