Microsoft KB Archive/309551

= INFO: CLR Profiling Services Problems =

Article ID: 309551

Article Last Modified on 7/14/2003

-

APPLIES TO


 * Microsoft Visual C++ .NET 2003 Standard Edition
 * Microsoft .NET Framework 1.1
 * Microsoft Visual C++ .NET 2002 Standard Edition
 * Microsoft .NET Framework 1.0

-



This article was previously published under Q309551



SUMMARY
This article provides a list of known problems with the Common Language Runtime (CLR) Profiling Services.



MORE INFORMATION
The following problems may occur when you use the CLR Profiling Services:  The ObjectAllocatedbyClass callback provides only an approximation of the number of objects that are allocated between two consecutive garbage collections.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

311273 ObjectAllocatedByClass Callback Does Not Return the Exact Number of Objects Allocated

 A probe function that is injected by the profiler may cause an unhandled exception if the miPreserveSig flag is not set.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

310827 PRB: Probe Function Injected by Profiler May Cause Unhandled Exception

 The profiler may receive a just-in-time (JIT) compilation event but not a function enter event if the function is executed on context-bound objects.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

310828 PRB: JIT-Compilation Event Received for Method but Not FunctionEnter Event

 A method whose ID is passed to an UnmangedToManagedTransition callback with the flag COR_PRF_TRANSITION_CALL may not be just-in-time compiled.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

312222 PRB: Profiler Does Not Receive JIT-Compilation Notifications for Method with Reason COR_PRF_TRANSITION_RETURN

 A method whose ID is passed to a ManagedToUnmanagedTransition callback with the reason COR_PRF_TRANSITION_RETURN may be a &quot;stub&quot; function, and therefore the profiler will not receive just-in-time compilation and function enter/leave events for this method.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

312220 Function Passed to UnmanagedToManagedTransition Callback Is Not JIT-Compiled

 The profiler may not receive transition-related notifications in some Interop scenarios. For example, no UnmanagedToManagedTransition will be received if CoCreateInstance results in a managed object.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

312225 BUG: You Do Not Receive Transition-Related Notifications in Interop Scenarios

 The profiler may receive an AssemblyUnloadFinished notification before the AssemblyLoadFinished notification if the CLR aborts the loading of the assembly.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

310832 PRB: You Receive the AssemblyUnloadFinished Notification Before the AssemblyLoadFinished Notification

</li> SetILInstrumentedCodeMap may cause an access violation if it is called from a JitCompilationStarted callback with the fJitStart flag set to &quot;FALSE&quot;.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

310833 SetILInstrumentedCodeMap May Cause Access Violation

</li> The .NET Profiling Service's remoting callbacks are unreliable. They may provide inaccurate information or cause the application that is being profiled to stop responding.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

310835 BUG: .NET Profiling Service Remoting Callbacks Are Unreliable

</li></ul>

<div class="references_section">