Below is a list of known issues with the profiler.
• Instance data are not collected for all classes when low-impact profiling is enabled under .NET Framework 2.0
• Roots are not always identified and instance fields data is not always available
Depending on the session settings, the profiler may fail to retrieve some static or instance fields, which will cause static fields roots to be missed, or instance data to not be collected.
• The docking windows in the details views have some quirks
The docking library used is not fully suitable for the “dash-board” type of docking windows used by the details views, so there is a risk that the window docking behaves strangely under some circumstances. If the layout becomes messed up, use the View->Layout->Reset layout command to reset the layout.
• Identification of generic type parameters under .NET Framework 2.0.
As discussed under Generic Methods, the actual type parameters cannot always be identified for generic methods. It is possible to make an implementation that identifies all type parameters for generic methods, but the performance overhead for this is high. Currently, there are no plans for implementing better identification of type parameters for generic methods.