This article provides a list of known problems with the
Common Language Runtime (CLR) Profiling Services.
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
(http://support.microsoft.com/kb/311273/EN-US/
)
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
(http://support.microsoft.com/kb/310827/EN-US/
)
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
(http://support.microsoft.com/kb/310828/EN-US/
)
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
(http://support.microsoft.com/kb/312222/EN-US/
)
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 "stub" 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
(http://support.microsoft.com/kb/312220/EN-US/
)
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
(http://support.microsoft.com/kb/312225/EN-US/
)
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
(http://support.microsoft.com/kb/310832/EN-US/
)
PRB: You Receive the AssemblyUnloadFinished Notification Before the AssemblyLoadFinished Notification
- SetILInstrumentedCodeMap may cause an access violation if
it is called from a JitCompilationStarted callback with the fJitStart flag set to "FALSE".For
additional information, click the article number below to view the article in
the Microsoft Knowledge Base:
310833
(http://support.microsoft.com/kb/310833/EN-US/
)
SetILInstrumentedCodeMap May Cause Access Violation
- 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
(http://support.microsoft.com/kb/310835/EN-US/
)
BUG: .NET Profiling Service Remoting Callbacks Are Unreliable
For other top-hit Visual C++ .NET KB articles, visit the
following Microsoft Web site:
Back to the top
