Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 Code Inspection crashes VS 2015 IDE
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

rpalma
Junior Member

Belgium
19 Posts

Posted - Mar 27 2017 :  03:44:31 AM  Show Profile  Reply with Quote
Hi,

There seems to be an issue with the Code Inspection feature, making VS 2015 crash completely. It seems to be related to the contents of some .cpp files, as the issue is consistently reproducible for the offending source files. Turning off code inspection fixes the crash issue.
The problem was already present in VA build 2210, but remains in build 2212.

Technical information:
VA_X.dll file version 10.9.2212.0 built 2017.03.23
DevEnv.exe version 14.0.25420.1 Professional
msenv.dll version 14.0.25431.1
Comctl32.dll version 6.10.10586.839
Windows 10 10.0 Build 10586
8 processors (x86-64, WOW64)
Language info: 1252, 0x813

Contents of VaCodeInspections.log:
[LI] loading
ERROR: Exception: The "CL" rule is missing the "LanguageStandard" property.
Callstack = at Microsoft.VisualStudio.ProjectSystem.Utilities.ProjectErrorUtilities.ThrowProjectExceptionHelper(Exception innerException, String unformattedMessage, Object[] args)

at Microsoft.VisualStudio.ProjectSystem.Utilities.ProjectErrorUtilities.ThrowProjectException(String message, Object arg0, Object arg1)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCRulePropertyStorage.<>c__DisplayClass5_0.<<GetEvaluatedPropertyValue>b__0>d.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.<>c__DisplayClass9_0`1.<<Invoke>b__0>d.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()

at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()

at Microsoft.VisualStudio.Threading.JoinableTaskFactory.Run[T](Func`1 asyncMethod, JoinableTaskCreationOptions creationOptions)

at Microsoft.VisualStudio.Threading.JoinableTaskFactory.Run[T](Func`1 asyncMethod)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.Invoke[TResult](Func`1 method)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCRulePropertyStorage.GetEvaluatedPropertyValue(String propertyName)

at WholeTomato.VaCodeInspections.VisualStudio.ProjectItemInspector.GetStdFlags(VCConfiguration vcConfig)
INFO: New FileParser: D:\[Development]\Dev_C2m_2015\Most Recent\Features\C2mUi\PowerFlex\PowerFlexGraphView.cpp
[BegTask 1.1] Parse
[EndTask 1.1] 3388ms
[BegTask 1.2] BufferListener.Deactivate
[EndTask 1.2] 69ms
ERROR: Exception: The "CL" rule is missing the "LanguageStandard" property.
Callstack = at Microsoft.VisualStudio.ProjectSystem.Utilities.ProjectErrorUtilities.ThrowProjectExceptionHelper(Exception innerException, String unformattedMessage, Object[] args)

at Microsoft.VisualStudio.ProjectSystem.Utilities.ProjectErrorUtilities.ThrowProjectException(String message, Object arg0, Object arg1)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCRulePropertyStorage.<>c__DisplayClass5_0.<<GetEvaluatedPropertyValue>b__0>d.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.<>c__DisplayClass9_0`1.<<Invoke>b__0>d.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()

at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()

at Microsoft.VisualStudio.Threading.JoinableTaskFactory.Run[T](Func`1 asyncMethod, JoinableTaskCreationOptions creationOptions)

at Microsoft.VisualStudio.Threading.JoinableTaskFactory.Run[T](Func`1 asyncMethod)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.Invoke[TResult](Func`1 method)

at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCRulePropertyStorage.GetEvaluatedPropertyValue(String propertyName)

at WholeTomato.VaCodeInspections.VisualStudio.ProjectItemInspector.GetStdFlags(VCConfiguration vcConfig)
INFO: New FileParser: D:\[Development]\Dev_C2m_2015\Most Recent\Features\C2mUi\PowerFlex\PowerFlexCanvasNavigatorView.cpp
[BegTask 2.1] Parse



feline
Whole Tomato Software

United Kingdom
16076 Posts

Posted - Mar 27 2017 :  09:26:41 AM  Show Profile  Reply with Quote
Can you please reproduce this and save out a mini dump of the crash, and then send us this mini dump please:

Please submit the files via the form:

http://www.wholetomato.com/support/contact.asp

including this thread ID or URL in the description, so we can match it up.

Also, if you have the time, can you please try opening one of these problem files in a new, default solution, and see if you still get this problem? I have tried opening one problem .c file here, but so far no crashes, so I am wondering if your files will cause a crash on their own, or if the solution context is also required.

zen is the art of being at one with the two'ness
Go to Top of Page

rpalma
Junior Member

Belgium
19 Posts

Posted - Mar 27 2017 :  10:51:11 AM  Show Profile  Reply with Quote
The VS mini dump has been submitted via the form.

These source files are part of a large solution, with a lot of dependencies. Copying only the contents of these to a new solution will end up in something that doesn't compile.
Anyway, I did that and in that case there is no crash.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
16076 Posts

Posted - Mar 27 2017 :  2:36:58 PM  Show Profile  Reply with Quote
Not being able to compile is expected, I was just wondering if the dependencies were required for the crash. Some problems can be reproduced with just a single file that does not compile, but obviously this is not one of these cases.

Thank you for checking, and also for sending in the mini dump.

zen is the art of being at one with the two'ness
Go to Top of Page

rpalma
Junior Member

Belgium
19 Posts

Posted - Mar 28 2017 :  03:23:23 AM  Show Profile  Reply with Quote
I can confirm that the crash issue is fixed when using the modified dll that was provided.

Thanks to the team for providing a quick solution!
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
16076 Posts

Posted - Mar 28 2017 :  06:51:28 AM  Show Profile  Reply with Quote
Thank you for the update, and the help in tracking down this problem.

zen is the art of being at one with the two'ness
Go to Top of Page

rpalma
Junior Member

Belgium
19 Posts

Posted - Apr 05 2017 :  06:44:09 AM  Show Profile  Reply with Quote
While one crash scenario has been fixed, unfortunately I have to report that turning on the Code Inspection feature still causes VS 2015 to crash frequently.

For now, I found one other scenario that is 100% reproducible: opening a certain .cpp file will cause VS 2015 to crash, only when Code Inspection is turned on. I will upload the VS 2015 mini dump via the contact form (FYI: I am still using the modified .dll file that was provided earlier). I also tried opening this file in VS 2017, which crashed as well.

Go to Top of Page

rpalma
Junior Member

Belgium
19 Posts

Posted - Apr 06 2017 :  04:43:42 AM  Show Profile  Reply with Quote
Thanks for providing me with a second modified .dll.

I can confirm that this specific crash scenario is resolved by using the modified .dll.

Go to Top of Page

sean
Whole Tomato Software

USA
2697 Posts

Posted - Apr 26 2017 :  5:09:14 PM  Show Profile  Reply with Quote
The crash fixes are available in build 2217.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000