| T O P I C R E V I E W |
| Shambler |
Posted - Aug 31 2017 : 07:39:34 AM
Exception:
The thread 0x47c8 has exited with code 0 (0x0).
The thread 0x3018 has exited with code 0 (0x0).
Exception thrown at 0x75B9C42D (KernelBase.dll) in devenv.exe: 0xE0434352 (parameters: 0x80131509, 0x00000000, 0x00000000, 0x00000000, 0x71D80000).
Exception thrown at 0x75B9C42D (KernelBase.dll) in devenv.exe: 0xE0434352 (parameters: 0x80131620, 0x00000000, 0x00000000, 0x00000000, 0x71D80000).
Exception thrown at 0x75B9C42D (KernelBase.dll) in devenv.exe: 0xE0434352 (parameters: 0x80131500, 0x00000000, 0x00000000, 0x00000000, 0x71D80000).
Unhandled exception at 0x75B9C42D in devenv.exe: Microsoft C++ exception: std::bad_alloc at memory location 0xDB69E864.
With the following callstack:
> KernelBase.dll!_RaiseException@16 () Unknown
valibclang.dll!274a4e0a() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for valibclang.dll]
valibclang.dll!2748de42() Unknown
valibclang.dll!2748c842() Unknown
valibclang.dll!26a562a5() Unknown
valibclang.dll!26a2d9fe() Unknown
valibclang.dll!26a31d93() Unknown
valibclang.dll!26a2e594() Unknown
valibclang.dll!26a3c603() Unknown
valibclang.dll!26a3d120() Unknown
valibclang.dll!26a3bec6() Unknown
valibclang.dll!26a2e07f() Unknown
valibclang.dll!26a3c237() Unknown
valibclang.dll!26a3a9ab() Unknown
valibclang.dll!26a3bdae() Unknown
valibclang.dll!26a2e07f() Unknown
valibclang.dll!26a3c237() Unknown
valibclang.dll!26a41a95() Unknown
valibclang.dll!26a3c062() Unknown
valibclang.dll!26a2e07f() Unknown
valibclang.dll!26a456fd() Unknown
valibclang.dll!26a52022() Unknown
valibclang.dll!27476bce() Unknown
valibclang.dll!26ff5c96() Unknown
valibclang.dll!26fc3515() Unknown
valibclang.dll!26fbecdb() Unknown
valibclang.dll!27478dc7() Unknown
valibclang.dll!26fba152() Unknown
valibclang.dll!26ff5c96() Unknown
valibclang.dll!27478d9b() Unknown
valibclang.dll!27479327() Unknown
valibclang.dll!27478859() Unknown
valibclang.dll!27479297() Unknown
valibclang.dll!2747934a() Unknown
valibclang.dll!27479778() Unknown
valibclang.dll!27476a1b() Unknown
valibclang.dll!27459871() Unknown
valibclang.dll!274700c7() Unknown
valibclang.dll!27473c73() Unknown
valibclang.dll!2746b99c() Unknown
valibclang.dll!2745fbf8() Unknown
valibclang.dll!27473898() Unknown
valibclang.dll!2746b99c() Unknown
valibclang.dll!27463f92() Unknown
valibclang.dll!274609e7() Unknown
valibclang.dll!27461511() Unknown
valibclang.dll!2746e11f() Unknown
valibclang.dll!27460bd4() Unknown
valibclang.dll!274614a2() Unknown
valibclang.dll!2745b154() Unknown
valibclang.dll!26ba4d3b() Unknown
valibclang.dll!26ba4d3b() Unknown
valibclang.dll!26ba4d3b() Unknown
valibclang.dll!2724c065() Unknown
valibclang.dll!26ba1461() Unknown
valibclang.dll!26ba139f() Unknown
valibclang.dll!26b72bf5() Unknown
valibclang.dll!26b71f54() Unknown
valibclang.dll!26b71c64() Unknown
valibclang.dll!269d10bd() Unknown
valibclang.dll!269c5d64() Unknown
valibclang.dll!26f6711a() Unknown
valibclang.dll!26f67194() Unknown
valibclang.dll!26f6722d() Unknown
valibclang.dll!274af201() Unknown
kernel32.dll!@BaseThreadInitThunk@12 () Unknown
ntdll.dll!___RtlUserThreadStart@8 () Unknown
ntdll.dll!__RtlUserThreadStart@8 () Unknown
System info:
VA_X.dll file version 10.9.2231.0 built 2017.08.15
DevEnv.exe version 14.0.25420.1 Professional
msenv.dll version 14.0.25431.1
Comctl32.dll version 6.10.7601.18837
Windows 7 6.1 Build 7601 Service Pack 1
12 processors (x86-64, WOW64)
Language info: 1252, 0x1809
I've saved a full + mini crash dump as well, if that'd be useful - but would be handy to avoid having to upload it somewhere, if the above info is enough.
I was performing a Alt+Shift+F code search when this happened, which had been going on for a long time.
In the previous VAX version, this happened with the Code Inspector enabled - it's not that which caused this again, is it?
I assume this is a memory usage error - is it at all possible, for VAX to be re-engineered to run in a 64bit process alongside the 32bit VS2015 process - so that stuff like this can't happen? |
| 9 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Nov 05 2017 : 09:21:42 AM
From the call stack, disabling Code Inspection should fix this problem. Is there any chance of getting a copy of the code file that triggered the crash, for testing purposes? I understand this is often not possible, but it's worth asking on the off chance.
Yes please, do send through the mini dump file via the contact support page:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up. |
| Shambler |
Posted - Nov 04 2017 : 1:59:51 PM
No I'm running Windows 7 - that new crash was a once off, and I was told it was actually a Visual Studio issue, rather than a VAX issue - so nevermind.
I came across the original std::bad_alloc crash again just now though, will send the crash dumps through the contact form, shortly. Here's the callstack, code inspection is enabled:
> KernelBase.dll!_RaiseException@16 () Unknown
valibclang.dll!274bb71a() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for valibclang.dll]
valibclang.dll!2748c296() Unknown
valibclang.dll!274a3150() Unknown
valibclang.dll!27052f16() Unknown
valibclang.dll!26a2d588() Unknown
valibclang.dll!26a2d9bb() Unknown
valibclang.dll!26a3d38f() Unknown
valibclang.dll!26a41696() Unknown
valibclang.dll!26a2e264() Unknown
valibclang.dll!26a3cfae() Unknown
valibclang.dll!26a3b822() Unknown
valibclang.dll!26a2db8f() Unknown
valibclang.dll!26a3bb57() Unknown
valibclang.dll!26a3a24b() Unknown
valibclang.dll!26a3b6ce() Unknown
valibclang.dll!26a2db8f() Unknown
valibclang.dll!26a3bb57() Unknown
valibclang.dll!26a3c985() Unknown
valibclang.dll!26a3b982() Unknown
valibclang.dll!26a2db8f() Unknown
valibclang.dll!26a4519d() Unknown
valibclang.dll!26a51b52() Unknown
valibclang.dll!2747991e() Unknown
valibclang.dll!27479ee9() Unknown
valibclang.dll!27025be6() Unknown
valibclang.dll!2747b6ed() Unknown
valibclang.dll!274798da() Unknown
valibclang.dll!270e5542() Unknown
valibclang.dll!27025be6() Unknown
valibclang.dll!2747bb3b() Unknown
valibclang.dll!2747c067() Unknown
valibclang.dll!2747c08a() Unknown
valibclang.dll!2747c4d8() Unknown
valibclang.dll!2747976b() Unknown
valibclang.dll!2745c461() Unknown
valibclang.dll!2746bab8() Unknown
valibclang.dll!27476a53() Unknown
valibclang.dll!2746e99c() Unknown
valibclang.dll!27460a02() Unknown
valibclang.dll!2747697b() Unknown
valibclang.dll!2746e99c() Unknown
valibclang.dll!27462968() Unknown
valibclang.dll!27476588() Unknown
valibclang.dll!2746e99c() Unknown
valibclang.dll!27467042() Unknown
valibclang.dll!274638c7() Unknown
valibclang.dll!274643f1() Unknown
valibclang.dll!27468edf() Unknown
valibclang.dll!27463ab4() Unknown
valibclang.dll!27464382() Unknown
valibclang.dll!2745dde4() Unknown
valibclang.dll!26ba5aeb() Unknown
valibclang.dll!26ba5aeb() Unknown
valibclang.dll!26ba5aeb() Unknown
valibclang.dll!2724e865() Unknown
valibclang.dll!26ba1ff1() Unknown
valibclang.dll!26ba1f2f() Unknown
valibclang.dll!26b73ee5() Unknown
valibclang.dll!26b73244() Unknown
valibclang.dll!26b72f54() Unknown
valibclang.dll!269d0d6d() Unknown
valibclang.dll!269c5a94() Unknown
valibclang.dll!26f693ea() Unknown
valibclang.dll!26f69464() Unknown
valibclang.dll!26f694fd() Unknown
valibclang.dll!274c5af1() Unknown
kernel32.dll!@BaseThreadInitThunk@12 () Unknown
ntdll.dll!___RtlUserThreadStart@8 () Unknown
ntdll.dll!__RtlUserThreadStart@8 () Unknown
|
| feline |
Posted - Nov 02 2017 : 10:50:03 AM
Are you running Windows 10, and if so, have you recently installed the Fall update for Windows 10? I ask since we are seeing some crashes there, due to this Windows update, so this is a possible factor.
Was this a one off crash, or have you been seeing regular problems over the last few days or weeks? |
| Shambler |
Posted - Nov 02 2017 : 08:15:01 AM
Here's a new crash on VAX 2235 (didn't update to latest, as changelog didn't note any crash fixes) - sent the new set of crash dumps on the contact form - Code Inspector is enabled.
It happened as I was adding a new virtual override function to a class, encapsulated in #if 1 #endif blocks, in UE4 - I added the definition to the header, switched to the .cpp to write the implementation, and it crashed before I could type anything.
Auto recovery failed to save this change to the header.
Callstack:
> vcpkg.dll!CEdgeFileBuf::Disconnect(bool) Unknown
vcpkg.dll!CEdgeSystem::DocumentClosing(unsigned short const *) Unknown
vcpkg.dll!CParserManager::DestroyTextNode(unsigned short const *) Unknown
vcpkg.dll!CParserManager::OnBeforeLastDocumentUnlock(unsigned long,unsigned long,unsigned long,unsigned long) Unknown
msenv.dll!<lambda>(void)() Unknown
msenv.dll!CCookieTable<class ATL::CComPtr<struct IVsRunningDocTableEvents>,struct DefaultCookieTraits<unsigned long,1,4294967295,0,1>,struct DefaultValueTraits<class ATL::CComPtr<struct IVsRunningDocTableEvents> > >::for_each<class <lambda_fe5d261692ec0f194a3ac4e067dd3512> >(class <lambda_fe5d261692ec0f194a3ac4e067dd3512>,bool) Unknown
msenv.dll!CRunningDocTable::Impl::NotifyOnBeforeLastUnlock(unsigned long,unsigned long,unsigned long,unsigned long) Unknown
msenv.dll!CRunningDocTable::NotifyOnBeforeLastUnlock(unsigned long,unsigned long,unsigned long,unsigned long) Unknown
msenv.dll!CRunningDocInfo::Unlock(unsigned long) Unknown
msenv.dll!CRunningDocTable::UnlockDocument(unsigned long,unsigned long) Unknown
rpcrt4.dll!_Invoke@12 () Unknown
rpcrt4.dll!_NdrStubCall2@16 () Unknown
ole32.dll!CStdStubBuffer_Invoke(IRpcStubBuffer * This, tagRPCOLEMESSAGE * prpcmsg, IRpcChannelBuffer * pRpcChannelBuffer) Line 1590 C++
ole32.dll!SyncStubInvoke(tagRPCOLEMESSAGE * pMsg, const _GUID & riid, CIDObject * pID, void * pVtableAddress, IRpcChannelBuffer * pChnl, IRpcStubBuffer * pStub, unsigned long * pdwFault) Line 1187 C++
ole32.dll!StubInvoke(tagRPCOLEMESSAGE * pMsg, CStdIdentity * pStdID, IRpcStubBuffer * pStub, IRpcChannelBuffer * pChnl, tagIPIDEntry * pIPIDEntry, unsigned long * pdwFault) Line 1396 C++
ole32.dll!CCtxComChnl::ContextInvoke(tagRPCOLEMESSAGE * pMessage, IRpcStubBuffer * pStub, tagIPIDEntry * pIPIDEntry, unsigned long * pdwFault) Line 1262 C++
ole32.dll!MTAInvoke(tagRPCOLEMESSAGE * pMsg, unsigned long CallCatIn, IRpcStubBuffer * pStub, IInternalChannelBuffer * pChnl, tagIPIDEntry * pIPIDEntry, unsigned long * pdwFault) Line 2105 C++
ole32.dll!STAInvoke(tagRPCOLEMESSAGE * pMsg, unsigned long CallCatIn, IRpcStubBuffer * pStub, IInternalChannelBuffer * pChnl, void * pv, tagIPIDEntry * pIPIDEntry, unsigned long * pdwFault) Line 1924 C++
ole32.dll!AppInvoke(CMessageCall * pCall, CRpcChannelBuffer * pChannel, IRpcStubBuffer * pStub, void * pv, void * pStubBuffer, tagIPIDEntry * pIPIDEntry, LocalThis * pLocalb) Line 1081 C++
ole32.dll!ComInvokeWithLockAndIPID(CMessageCall * pCall, tagIPIDEntry * pIPIDEntry) Line 1724 C++
ole32.dll!ComInvoke(CMessageCall * pCall) Line 1469 C++
ole32.dll!ThreadDispatch(void * param) Line 298 C++
ole32.dll!ThreadWndProc(HWND__ * window, unsigned int message, unsigned int wparam, long params) Line 598 C++
user32.dll!_InternalCallWinProc@20 () Unknown
user32.dll!_UserCallWinProcCheckWow@32 () Unknown
user32.dll!_DispatchMessageWorker@8 () Unknown
user32.dll!_DispatchMessageW@4 () Unknown
VA_X.dll!0bf79d0d() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for VA_X.dll]
ole32.dll!CCliModalLoop::SendReceive(tagRPCOLEMESSAGE * pMsg, unsigned long * pulStatus, IInternalChannelBuffer * pChnl) Line 899 C++
ole32.dll!CAptRpcChnl::SendReceive(tagRPCOLEMESSAGE * pMsg, unsigned long * pulStatus) Line 583 C++
ole32.dll!CCtxComChnl::SendReceive(tagRPCOLEMESSAGE * pMessage, unsigned long * pulStatus) Line 659 C++
ole32.dll!NdrExtpProxySendReceive(void * pThis, _MIDL_STUB_MESSAGE * pStubMsg) Line 1932 C++
rpcrt4.dll!@NdrpProxySendReceive@4 () Unknown
rpcrt4.dll!_NdrClientCall2 () Unknown
ole32.dll!ObjectStublessClient(void * ParamAddress, long Method) Line 474 C++
ole32.dll!_ObjectStubless@0() Line 154 Unknown
vcpkg.dll!CEdgeSystem::Reset(unsigned int,unsigned short const * * const,bool) Unknown
vcpkg.dll!CParserManager::SolutionCloseAndCfgChangeHelper(struct IUnknown *,bool) Unknown
vcpkg.dll!CParserManager::OnBeforeCloseSolution(struct IUnknown *) Unknown
msenv.dll!CSolution::NotifySolutionEventsSinks<class <lambda_d4eaebae4fc7b18ad08f764ac4d2ad55> >(class <lambda_d4eaebae4fc7b18ad08f764ac4d2ad55>) Unknown
msenv.dll!CSolution::NotifyOnBeforeCloseSolution(struct IUnknown *) Unknown
msenv.dll!CSolution::Close(int,int,int) Unknown
msenv.dll!_MainClose(void) Unknown
msenv.dll!VStudioMainLogged(void) Unknown
msenv.dll!_VStudioMain () Unknown
devenv.exe!util_CallVsMain(struct MAINPARAM *,int *) Unknown
devenv.exe!CDevEnvAppId::Run(unsigned short *,int) Unknown
devenv.exe!_WinMain@16 () Unknown
devenv.exe!__scrt_common_main_seh() Unknown
kernel32.dll!@BaseThreadInitThunk@12 () Unknown
ntdll.dll!___RtlUserThreadStart@8 () Unknown
ntdll.dll!__RtlUserThreadStart@8 () Unknown
|
| Shambler |
Posted - Sep 16 2017 : 12:43:21 PM
Sent a new set of crash dumps - this seems like it may be related to using VS2015 when debugging a program that's crashed - but may not be the only case. |
| accord |
Posted - Sep 13 2017 : 1:22:19 PM
The conversation continues via email. |
| Shambler |
Posted - Sep 02 2017 : 10:02:20 PM
Thanks! I've sent both the mini + full dump to the contact form there. Code Inspector running in a different process sounds good alright - very nice feature, will switch it back on in the next release. |
| sean |
Posted - Aug 31 2017 : 1:06:29 PM
Sorry, yes, the crash is due to Code Inspection (per the valibclang.dll addresses in the callstack). Code Inspection is a beta feature. It will not be out of beta until, at a minimum, the logic is moved to an external process so that valibclang crashes do not bring down Visual Studio. case=104069 |
| feline |
Posted - Aug 31 2017 : 10:06:39 AM
Can you please send us the mini dump, and possibly the full dump as well, depending on how large it is compressed, and how much time you have to leave this uploading. 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.
From the call stack, yes, this is related to Code Inspection, so can you please try turning off Code Inspection, and see if this makes any difference?
As for 64bit vs 32bit, we are restricted by the fact that we are running in the IDE's context, which is a 32bit process. There should not be any memory leaks in VA, but that's the difference between what should be and what is. |
|
|
