CPU Profiling crashes with BEX64 - by CadErikWork

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 771645 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 11/19/2012 1:03:24 PM
Access Restriction Public


We tried profiling one of our application (it worked perfectly on vs 10) and every time we reach a certain point in the execution, the profiler crashes with a BEX64 crash. The same behavior was experienced on 2 different computers.

This is the stack trace for the BEX64 exception
>	clr.dll!__crt_debugger_hook\u001e()	Unknown
 	clr.dll!__raise_securityfailure\u001e()	Unknown
 	clr.dll!__report_gsfailure\u001e()	Unknown
 	clr.dll!StackFrameIterator::Init(class Thread *,class Frame *,struct REGDISPLAY *,unsigned int)	Unknown
 	clr.dll!Thread::StackWalkFramesEx(struct REGDISPLAY *,enum StackWalkAction (*)(class CrawlFrame *,void *),void *,unsigned int,class Frame *)	Unknown
 	clr.dll!Thread::StackWalkFrames(enum StackWalkAction (*)(class CrawlFrame *,void *),void *,unsigned int,class Frame *)	Unknown
 	clr.dll!ProfToEEInterfaceImpl::ProfilerStackWalkFramesWrapper(class Thread *,struct _PROFILER_STACK_WALK_DATA *,unsigned int)	Unknown
 	clr.dll!ProfToEEInterfaceImpl::DoStackSnapshotHelper(class Thread *,struct _PROFILER_STACK_WALK_DATA *,unsigned int,struct _CONTEXT *)	Unknown
 	clr.dll!ProfToEEInterfaceImpl::DoStackSnapshot(unsigned __int64,long (*)(unsigned __int64,unsigned __int64,unsigned __int64,unsigned int,unsigned char * const,void *),unsigned int,void *,unsigned char *,unsigned int)	Unknown
 	VSPerfCorProf.dll!IsStackWalkSafe(void)	Unknown
 	SamplingRuntime.dll!operator delete(void *,void *)	Unknown
 	SamplingRuntime.dll!ImageLoadNotify(struct _PUSHAD_CONTEXT *,void * *)	Unknown
 	SamplingRuntime.dll!ProcessSample\u001e()	Unknown
 	SamplingRuntime.dll!GetSample\u001e()	Unknown
Sign in to post a comment.
Posted by ww898 on 4/19/2013 at 6:27 AM
I'm not sure that I have the same bug. However, I have the stack trace like above. All information about the bug is here: http://youtrack.jetbrains.com/issue/PROF-53.
Posted by Microsoft on 3/20/2013 at 9:05 AM
Oh, and one other thing. It *appears* that the issue you're hitting may be limited to amd64 processes. If you can produce x86 builds of your product and perform profiling on that, you may be able to avoid this. However, I don't know if that's possible in your case, and we cannot definitely identify the problem so I could be wrong about this advice. Still, we'd definitely like to know if you can reproduce this on x86. And a complete dump with full heap will help significantly with us diagnosing the exact issue.
Posted by Microsoft on 3/20/2013 at 9:01 AM
Hello, and thanks for sending us the minidump. It was helpful to narrow down the issue to some degree, but unfortunately not enough to definitively pinpoint the exact problem. Would it be possible for you to submit a complete dump with full heap information? For example, you can generate one in windbg via ".dump /ma".

Thanks again for the information you have provided so far.
Posted by CadErikWork on 11/23/2012 at 7:36 AM
I submitted a minidump file for the issue.
Posted by Microsoft on 11/22/2012 at 5:19 PM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested . If we haven't heard back from you with the requested information in the next 3 days, we will go ahead and close the issue.
Posted by Microsoft on 11/19/2012 at 6:31 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a dmp file. Please submit this information to us within 4 business days. We look forward to hearing from you with this information.
Posted by Macy [MSFT] on 11/19/2012 at 1:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)