Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Crash in valibclang.dll with VS2017 15.5

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
alex.postlethwaite Posted - Dec 06 2017 : 07:38:49 AM
The crash keeps getting caught by WER, so I assume you are aware of it (but I do have a minidump if you want me to upload it?)

The report on my computer is:

Description
Faulting Application Path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: devenv.exe
Application Version: 15.0.27130.0
Application Timestamp: 5a20cf11
Fault Module Name: valibclang.dll
Fault Module Version: 10.9.2238.2
Fault Module Timestamp: 5a04fe30
Exception Code: c0000005
Exception Offset: 009594d1
OS Version: 10.0.16299.2.0.0.256.48
Locale ID: 2057
Additional Information 1: bfa1
Additional Information 2: bfa1645468363822351bfb5370af13e4
Additional Information 3: 1412
Additional Information 4: 14120fc2984bc34ce6410afaf40eec21


VAX info:
VA_X.dll file version 10.9.2238.2 built 2017.11.10
DevEnv.exe version 15.0.27130.0 Professional
msenv.dll version 15.0.27128.1
Comctl32.dll version 6.10.16299.98
Windows 10 10.0 Build 16299
8 processors (x86-64, WOW64)
Language info: 1252, 0x809

Platform: Win32
Stable Includes:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.12.25827\include;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.12.25827\atlmfc\include;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\include;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt;
C:\Program Files (x86)\Windows Kits\8.1\Include\um;
C:\Program Files (x86)\Windows Kits\8.1\Include\shared;
C:\Program Files (x86)\Windows Kits\8.1\Include\winrt;

Other Includes:

Stable Source Directories:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.12.25827\atlmfc\src\mfc;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.12.25827\atlmfc\src\mfcm;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.12.25827\atlmfc\src\atl;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.12.25827\crt\src;
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\VS\src;
C:\Program Files (x86)\Windows Kits\10\Source\10.0.10240.0\ucrt;

5   L A T E S T    R E P L I E S    (Newest First)
alex.postlethwaite Posted - Dec 20 2017 : 05:03:55 AM
Thanks sean, lgtm.

alex
sean Posted - Dec 18 2017 : 7:20:17 PM
case=112698 is fixed in build 2248
sean Posted - Dec 06 2017 : 10:36:25 AM
Non-exe applications are being cut off from Windows Error Reporting. We no longer have access to reports of crashes in our dlls that are reported to Microsoft.

We are aware of the Code Inspection crash that occurs in VS2017 15.5. It will be addressed in our next release. case=112698
alex.postlethwaite Posted - Dec 06 2017 : 09:40:23 AM
Thanks. I've uploaded a minidump.

I think one repro is:

* Create a new win32 console application.
* add #include <algorithm>
* wait a moment for the reparse to kick in, and devenv should crash.
feline Posted - Dec 06 2017 : 08:13:32 AM
Can you please upload the minidump 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.

If you turn Off:

VA Options -> Code Inspection (beta) -> Enable Code Inspection

this should fix the crash. If you have time, and can reproduce this crash on demand, it would be interesting and useful to try and pin down the trigger. Sometimes it is a specific code file that causes the problem, if so, and you were able to share a copy of the file for testing purposes, I could try to figure out which part of the file is causing the problem.

© 2021 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000