Bug 40843 - Broken and incomplete GC logging
Summary: Broken and incomplete GC logging
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: GC ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-05-03 22:14 UTC by Rodrigo Kumpera
Modified: 2016-05-03 22:14 UTC (History)
2 users (show)

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 for Bug 40843 on GitHub or 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 original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Rodrigo Kumpera 2016-05-03 22:14:43 UTC
Reference: https://gist.githubusercontent.com/Krumelur/b8428bc14d03f0a569ed8f5b988f1281/raw/618f72b167e39660f963c5a6246a3df061296aef/GC.txt

From the above log file we can notice 2 things:

Bridge time reporting is broken, the fine grained log includes more time than what's reported on the aggregate one.

The "GC_BRIDGE waiting for bridge processing to finish" lines don't include for how long we waited for the GC.

We might be suffering from lock biasing on some workloads by this message gives us no hint at all.