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
 Devenv crashes when opening the VA Code Inspection
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

alex.postlethwaite
Senior Member

38 Posts

Posted - Jan 29 2020 :  06:48:04 AM  Show Profile  Reply with Quote
Devenv crashes when opening the VA Code Inspection Results window.

Open devenv without any projects loaded
Open the code inspection results window from the VAX menu.
Devenv crashes.

The window works fine in VS 2017, but not in 2019.

Version 16.4.3

License: Named Network User / Standard Support ends 2020.07.26
VA_X.dll file version 10.9.2358.0 built 2019.12.19
DevEnv.exe version 16.4.29709.97 Enterprise
msenv.dll version 16.0.29709.11
Comctl32.dll version 6.10.17763.831
Windows 10 10.0 1809 Build 17763.973
8 processors (x86-64, WOW64)
Language info: 1252, 0x809

Platform: Project defined
Stable Includes:
C:\Program Files (x86)\Windows Kits\NETFXSDK\4.7.2\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\2019\Enterprise\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\2019\Enterprise\VC\Auxiliary\VS\include;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.24.28314\atlmfc\include;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.24.28314\include;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\cppwinrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\winrt;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\shared;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\um;
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\ucrt;

Other Includes:

Stable Source Directories:
C:\Program Files (x86)\Windows Kits\10\Source\10.0.15063.0\ucrt;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\VS\src;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.24.28314\crt\src;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.24.28314\atlmfc\src\atl;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.24.28314\atlmfc\src\mfcm;
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.24.28314\atlmfc\src\mfc;
C:\Program Files (x86)\Windows Kits\10\Source\10.0.18362.0\ucrt;



I have a minidump available if needed.

Thanks,
alex

feline
Whole Tomato Software

United Kingdom
16339 Posts

Posted - Jan 29 2020 :  07:59:06 AM  Show Profile  Reply with Quote
Ouch, thank you for saving out a mini dump. I have emailed you about this:

case=141814

So far I cannot reproduce this here, but hopefully we can get to the bottom of this fairly soon.

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

alex.postlethwaite
Senior Member

38 Posts

Posted - Feb 17 2020 :  08:33:37 AM  Show Profile  Reply with Quote
quote:
Originally posted by feline

Ouch, thank you for saving out a mini dump. I have emailed you about this:



Hi,

Any news on the materials I uploaded?

Thanks.
Go to Top of Page

sean
Whole Tomato Software

USA
2763 Posts

Posted - Feb 17 2020 :  2:51:30 PM  Show Profile  Reply with Quote
It looks like we dropped the ball on communicating with you. The problem is fixed for the next release which is due this week. In the meantime, you should be able to prevent the problem by using the registry to change the value of ColumnLevel_Width to something like 30 at
HKEY_CURRENT_USER\Software\Whole Tomato\Visual Assist X\VANet16\CodeInspections\ToolWindow
Go to Top of Page

alex.postlethwaite
Senior Member

38 Posts

Posted - Feb 18 2020 :  05:03:39 AM  Show Profile  Reply with Quote
quote:
Originally posted by sean

It looks like we dropped the ball on communicating with you. The problem is fixed for the next release which is due this week. In the meantime, you should be able to prevent the problem by using the registry to change the value of ColumnLevel_Width to something like 30 at
HKEY_CURRENT_USER\Software\Whole Tomato\Visual Assist X\VANet16\CodeInspections\ToolWindow




Thanks, that field was 0x80000000 for whatever reason. It opens again now.
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