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 for Bug 51498 on
Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
Created attachment 19318 [details]
No count column visible
There used to be a "Count" column in the Xamarin Profiler Mac UI (Time Profiler). It has suddenly disappeared. Now I only have
* Running Time
* Symbol Name
I can't remember doing anything that could have triggered this (no updates or anything of that kind).
This was because we used method enter/leave before for getting timing information, which hits hard the performance of the app being profiled and is not as accurate as what we use now, sampling. And, when using sampling, we don't know how many times a method was called, like we used to get when using method enter/leave.
We might want to add an option to allow method enter/leave instead of sampling if the user chooses to.
An option to use enter/leave functionality instead of sampling would indeed be nice. The amount of times a method was called seems very important to me when trying to understand a profiling result. When a lot of time is spent in 1 method it could be because the method is doing some heavy stuff or it is just being called a lot and the problem is elsewhere.
Or maybe, when using sampling, we could display the number of samples for that method, instead of the count call. I think this might be better than resurrecting method enter/leave, which we don't want to offer to the user, as it degrades performance so much, than profiling becomes useless
Moving to future milestone.