Bug 43896 - Generate a finalizer report based on the new finalization events
Summary: Generate a finalizer report based on the new finalization events
Status: RESOLVED INVALID
Alias: None
Product: Runtime
Classification: Mono
Component: Profiler ()
Version: master
Hardware: All All
: Normal enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Alex Rønne Petersen
URL:
Depends on:
Blocks:
 
Reported: 2016-08-31 12:10 UTC by Alex Rønne Petersen
Modified: 2017-06-20 04:43 UTC (History)
0 users

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED INVALID

Description Alex Rønne Petersen 2016-08-31 12:10:54 UTC
We now emit the following events in the format:

* TYPE_GC_FINALIZE_START
* TYPE_GC_FINALIZE_END
* TYPE_GC_FINALIZE_OBJECT_START
* TYPE_GC_FINALIZE_OBJECT_END

It would be nice if mprof-report could generate a report with how many finalizers were executed per class, how long they took on average, lowest/highest execution time per class, etc.
Comment 1 Alex Rønne Petersen 2017-06-20 04:43:35 UTC
This will be part of a larger effort to rewrite mprof-report in C# using the new Mono.Profiler.Log library.