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
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.
Created attachment 8741 [details]
A screen-shot of a timer profiler session with wrong running time descending ordering
At the Time Profiler section > Call Tree > Running Time column, trying to order it either descendingly or ascendingly is not working very well as can be seen in the attached screen-shot. That would make much easier navigating the tree through the more time consuming calls.
Are you using the Evolve 0.9 version?
Hi José Miguel,
How can I find the exact version number? If I'm not wrong, you presented a preview at the Evolve conference and a few weeks later a second preview. It's that second preview the version that I'm using.
Forgot to mention it's the Windows version of the Profiler.
Never mind. This has been fixed weeks ago. So it's something will work for sure on the next release. I am about to close this record. Please, feel free to open it again or create a new one if you come across with any other issue on the Profiler.
Thanks for your time!
I have checked this issue with XamarinProfiler.Windows.Installer.0.11-84.msi
and this issue has been fixed now. Hence closing this issue.