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.
Created attachment 3854 [details]
test.cs that takes a while to execute
mono --profile=log:output=-output.mlpd,zip,noalloc,maxframes=8 test.exe
mprof-report --traces --time=1-2 --method-sort=self --alloc-sort=bytes --verbose output.mlpd > 1second
mprof-report --traces --time=2-4 --method-sort=self --alloc-sort=bytes --verbose output.mlpd > 2seconds
diff 1second 2seconds
There will be no output from the diff, indicating that the --time option does not do anything at all.
Paolo, do you plan on work on this?
Hey, I've found this bug while trying to make --time flag work.
It'd quite useful for our company to find the culprit for a performance issue.
Any ETA on this? Thanks in advance for your work guys!
There are a few fixes now in git to make the --time option more useful, previously it basically only handled allocations.
Note that for method enter/leave events that cross the time boundaries there can be inconsistencies, since we may consider either the enter or leave events, but not the matching leave/enter, so some of the timings will look wrong. I suggest using the sample mode for this case and you'll only get the sample events for the chosen timeframe.