Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
The classlibs use DebuggerDisplayAttribute in various places to improve debugging. Unfortunately, there are a few that refer to several properties, and therefore cause multiple getter invocations. Since debugger method invocations are extremely expensive, these could have a noticeable effect on performance. We could ameliorate it by using the trick described in this post of using a private property to do the expression evaluation and formatting, and have the DebuggerDisplayAttribute display just that property:
We may also need to add the ",nq" support to MD.
Where is missing DebuggerDisplayAttribute ?
Grep Mono sources, you will see several DebuggerDisplayAttributes that refer to multiple properties. They're not missing, this is a just a suggestions for improving perf by reducing the number of method invocations when displaying such objects.
There does not seem any in mono master