Visual Studio 2017 crashes - visual-studio-2017

The crashing is largely occurring when I start adding reports to different projects. The more I do, the worse it gets, but it typically doesn't take long before it freezes up.
My first thought was to check Event Viewer to see what I was getting, but I'm not quite sure what to make of it (SSRS developer, not thoroughly experienced with VS troubleshooting or .NET in general).
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at System.Drawing.Graphics.FromHdcInternal(IntPtr)
at System.Drawing.Font.GetHeight()
at System.Drawing.Font.get_Height()
at System.Windows.Forms.GroupBoxRenderer.DrawThemedGroupBoxWithText(System.Drawing.Graphics, System.Drawing.Rectangle, System.String, System.Drawing.Font, System.Drawing.Color, System.Windows.Forms.TextFormatFlags, System.Windows.Forms.VisualStyles.GroupBoxState)
at System.Windows.Forms.GroupBoxRenderer.DrawGroupBox(System.Drawing.Graphics, System.Drawing.Rectangle, System.String, System.Drawing.Font, System.Windows.Forms.TextFormatFlags, System.Windows.Forms.VisualStyles.GroupBoxState)
at System.Windows.Forms.GroupBox.OnPaint(System.Windows.Forms.PaintEventArgs)
at System.Windows.Forms.Control.PaintWithErrorHandling(System.Windows.Forms.PaintEventArgs, Int16)
at System.Windows.Forms.Control.OnPrint(System.Windows.Forms.PaintEventArgs)
at System.Windows.Forms.Control.WmPrintClient(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.GroupBox.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.TextBoxBase.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.TextBox.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
Then there's another Error 1 second after this one:
Faulting application name: devenv.exe, version: 15.9.28307.1093, time stamp: 0x5e93584b
Faulting module name: KERNELBASE.dll, version: 10.0.18362.997, time stamp: 0xd5511be4
Exception code: 0xe0434352
Fault offset: 0x001140b2
Faulting process id: 0x73d4
Faulting application start time: 0x01d68ac284d7cc95
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2017\SQL\Common7\IDE\devenv.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll
Report Id: 13d4e226-4630-4215-aab4-e8d382080996
Faulting package full name:
Faulting package-relative application ID:
The only extension I'm using is Visual SVN. Something I have already tried is removing it, but I still get crashes.

Never could figure out why it crashes, but I at least appear to have resolved my issue by running VS 2019 and installing the MS SSRS extension. I was able to load my pre-existing solution, and while I had to manually reload my projects, it's working well so far. Hope this helps others.

Related

ijwhost.dll exception when loading managed CLI C++ project compiled for /clr:netcore

I am running into an issue with my solution that is comprised of a native C++ application calling a managed C++ (CLR) that is in turn referencing a C# project.
(Typical native to managed bridge implementation)
The code compiles and runs successfully on my development machine. However once I move it to a staging server I get the following error:
Faulting application name: POC_MOCK.exe, version: 0.0.0.0, time stamp: 0x62c75fef
Faulting module name: ucrtbase.DLL, version: 10.0.14393.2990, time stamp: 0x5caeb859
Exception code: 0xc0000409
Fault offset: 0x000884cb
Faulting process id: 0x1c9c
Faulting application start time: 0x01d8927e8d0fe66f
Faulting application path: D:\test\POC_MOCK.exe
Faulting module path: C:\Windows\SYSTEM32\ucrtbase.DLL
Report Id: cad1e77c-fe71-11ec-80fe-000c297ddf34
Faulting package full name:
Faulting package-relative application ID:
Upon investigating the crash dump via winDBG, I saw that ijwhost.dll is causing an exception.
STACK_TEXT:
00e2fc60 5e00c672 e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x48
00e2fc90 5e001405 00e2fcb0 5e015750 00f58fe8 Ijwhost!_CxxThrowException+0x66
00e2fcdc 5e009d4c 013c0667 00000000 00f5dc20 Ijwhost!start_runtime_and_get_target_address+0x138
00e2fcf0 5e0b1fc5 c42602c1 00f5a430 00f5dc20 Ijwhost!start_runtime_thunk_stub+0xc
00e2fd10 01201041 9b12698d 73d9cf33 9b12698d CPPWrapper!CPPWrapper::CPPWrapper+0x45
00e2fd30 0120159c 00000001 00f5a430 00f58fe8 POC_MOCK!main+0x41
00e2fd78 74bd6a14 7f218000 74bd69f0 eefe366c POC_MOCK!__scrt_common_main_seh+0xfa
00e2fd8c 7712a9ff 7f218000 ed2f7874 00000000 kernel32!BaseThreadInitThunk+0x24
00e2fdd4 7712a9ca ffffffff 7710fdc7 00000000 ntdll!__RtlUserThreadStart+0x2f
00e2fde4 00000000 01201624 7f218000 00000000 ntdll!_RtlUserThreadStart+0x1b
FAULTING_SOURCE_LINE: D:\a\_work\1\s\src\installer\corehost\cli\ijwhost\ijwthunk.cpp
FAULTING_SOURCE_FILE: D:\a\_work\1\s\src\installer\corehost\cli\ijwhost\ijwthunk.cpp
FAULTING_SOURCE_LINE_NUMBER: 153
FAULTING_SOURCE_CODE:
No source found for 'D:\a\_work\1\s\src\installer\corehost\cli\ijwhost\ijwthunk.cpp'
SYMBOL_NAME: ijwhost!start_runtime_and_get_target_address+138
MODULE_NAME: Ijwhost
IMAGE_NAME: Ijwhost.dll
STACK_COMMAND: .cxr 0xe2f920 ; kb
FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_CPP_EXCEPTION_c0000409_Ijwhost.dll!start_runtime_and_get_target_address
OS_VERSION: 6.3.9600.18217
BUILDLAB_STR: winblue_ltsb
OSPLATFORM_TYPE: x86
OSNAME: Windows 8.1
IMAGE_VERSION: 5.0.1722.21314
FAILURE_ID_HASH: {b2047410-307d-cb83-9a4d-78b763edf2d5}
Followup: MachineOwner
I have no idea why Ijwhost::start_runtime_and_get_target_address is failing.
This seems to be a bit different than most of the issues I was able to find via google and on StackOverflow, so having tried some of the suggestions there didn't work for me.
ijwhost.dll does exist after a successful build and is next to the .EXE and .DLLs.
As seen in the above stack trace, the issue is happening when CPPWrapper is being constructed, and I took out all the references to anything C# and still got the error.
So just trying to call the constructor of the CLR DLL is where it goes bad.
Any hints, feedback is greatly appreciated!
Dev. evn.:
Win 10 professional, VS2022, VC++ v143, .NET6 and .NetCore 3.1
Staging env.:
Win Server 2012, required packages installed for the project to work and confirmed .net core 3.1 is installed for both x86 and x64 to be on the safe side.

Faulting module name: ntdll.dll, version: 6.3.9600.19678 Exception code: 0xc0000005

I had a VC++ project (console application) built on VS2013. It was working successfully for a long time. Recently we have converted that project to VS2019 (PlatformToolset 142). Now the latest exe is crashing after some operation with below error.
Faulting application name: abc.exe, version: 0.0.0.0, time stamp:
0x5eb3101a Faulting module name: ntdll.dll, version: 6.3.9600.19678,
time stamp: 0x5e82c88a Exception code: 0xc0000005 Fault offset:
0x0000000000030837 Faulting process id: 0x137c Faulting application
start time: 0x01d624424de8d7e1 Faulting application path: Faulting
module path: C:\Windows\SYSTEM32\ntdll.dll Report Id:
8bad3b06-9035-11ea-80de-d6b5b2fa72df Faulting package full name:
Faulting package-relative application ID:
One big observation is VS2019 exe is half size of VS2013 exe. How to debug further to find out the root cause of the application crash?
After run-in remote debug found that it is throwing an unhandled exception at
HeapAlloc( m_hHeap, HEAP_NO_SERIALIZE, _Count * sizeof( value_type ));
This was working perfectly with VC2013. This HeapAlloc issue I am getting whenever we are calling std::vector related operation. Is anything got change related to this in VS2019/VC++2019 ?

My app crashed caused by ucrtbase.dll. What does it mean? Where should I look for bug in my code?

I use Qt 5.10.1 64 bit, msvc2017-64, all dlls from the redistributable package are included. It happened just once, I can not reproduce it.
Problem Event Name: APPCRASH
Application Name: eyeblink.exe
Application Version: 3.1.2.0
Application Timestamp: 5acb80c8 Fault
Module Name: ucrtbase.DLL
Fault Module Version: 10.0.14393.2247
Fault Module Timestamp: 5adc1d0b
Exception Code: 40000015
Exception Offset: 000000000006eacf
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1051
Additional Information 1: 53f4
Additional Information 2: 53f453b2107907ea889c32b664ccee74
Additional Information 3: c023
Additional Information 4: c023e69e5a570b66998367aafd38badf

Windows Application crashes when executed without admin privileges but works find in debug mode in visual studio

Application Error :
Faulting application name: SynchroOutlookSynchronizer.exe, version: 1.0.6732.25647, time stamp: 0x5b18db78 Faulting module name: KERNELBASE.dll, version: 10.0.15063.1029, time stamp: 0x008ecb0e Exception code: 0xe0434352 Fault offset: 0x000000000006a1a8 Faulting process id: 0x968 Faulting application start time: 0x01d3fe3b34e682b4 Faulting application path: C:\Program Files (x86)\Atemis\OutlookSynchronizer\SynchroOutlookSynchronizer.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: f61ba8c3-c910-4345-9bb7-3a23b797a070 Faulting package full name: Faulting package-relative application ID:
Windows Error Reporting :
Fault bucket 1514048743125354531, type 5 Event Name: CLR20r3 Response: Not available Cab Id: 0
Problem signature: P1: SynchroOutlookSynchronizer.exe P2: 1.0.6732.25647 P3: 5b18db78 P4: mscorlib P5: 4.7.2650.0 P6: 5ab1c3d4 P7: 1672 P8: 12f P9: System.UnauthorizedAccess P10:
Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB425.tmp.mdmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB475.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB474.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB484.tmp.txt \?\C:\Users\LENOVO\AppData\Local\Temp\WERBBE8.tmp.appcompat.txt \?\C:\Users\LENOVO\AppData\Local\Temp\WERBBE9.tmp.WERDataCollectionStatus.txt
These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SynchroOutlookSy_fc7c8d8525d22403e3c521f7a60c1997c20bfdf_d8a74bc5_2afcbbf5
Analysis symbol: Rechecking for solution: 0 Report Id: c5065eee-a663-403e-a652-3558d3d71c46 Report Status: 2147487752 Hashed bucket: d48596f15ac524c75502fb4f629d0823
I am using & altering current user registry at some points in my code

Faulting module path: C:\Windows\system32\KERNELBASE.dll

I have a .Net 4.0 C++ application that used to be built in 32bits. Obviously when running on a 64bits station I was having issues, therefore I started rebuilding everything in 64 bits. The whole project is converted as well as the libraries I had made for this in other project files. All references have been updated and everything compiles fine.
Once deployed to a 64bit station I now get the following errors in the windows event viewer:
Information : Windows Error Reporting
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: EDI.exe
P2: 0.0.0.0
P3: 4e32e547
P4: KERNELBASE.dll
P5: 6.1.7601.17625
P6: 4de88429
P7: e0434352
P8: 000000000000cacd
P9:
P10:
Attached files:
These files may be available here:
C:\Users\developer\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_EDI.exe_b14cfebcf86ccaf91a35dacab06a28cdf7277ba_17f14701
Analysis symbol:
Rechecking for solution: 0
Report Id: c9983227-ba04-11e0-9299-002713d66c71
Report Status: 0
Error : Application Error
Faulting application name: EDI.exe, version: 0.0.0.0, time stamp: 0x4e32e547
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17625, time stamp: 0x4de88429
Exception code: 0xe0434352
Fault offset: 0x000000000000cacd
Faulting process id: 0x1704
Faulting application start time: 0x01cc4e118bde9f1d
Faulting application path: C:\Users\developer\Desktop\EDI_6.1.0.4160_x64\EDI_6.1.0.4160_x64\EDI.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c9983227-ba04-11e0-9299-002713d66c71
Error : .Net Runtime
Application: EDI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Stack:
at <Module>.main(System.String[])
When I run dependency walker on the executable, I get to see the executable listed in the modules and nothing else at all comes up. I am kind of out of ideas at the moment and wondering if anyone can make something of this?
Exception code: 0xe0434352
Not very common. Check this:
http://social.msdn.microsoft.com/Forums/en-GB/pex/thread/b9728c2d-130e-48f9-80c1-442ddbc1e85b
I just experienced this same error-code, also in Kernelbase.dll when attempting to debug a C++ application in VS2012. Fortunately in my case I tracked the issue down to the Document Well (from Productivity Powertools Extension) option:
Environment-Tabs and Windows-Maintain pin status if document is removed from well.
Clearing this option fixed my problem. It appears that DevStudio was crashing when rearranging the tabs/windows for debugging.
This may not be the cause of your particular issue, but I've added it here because if anyone else searches for error code: 0xe0434352 in Kernelbase.dll, this issue is at the top of the Google search.