Bug 46467 - The profiler does not record frames
Summary: The profiler does not record frames
Alias: None
Product: Profiler
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: PC Windows
: High normal
Target Milestone: (C8)
Assignee: Rodrigo Moya
Depends on:
Reported: 2016-11-04 13:30 UTC by Jerome Laban
Modified: 2016-11-10 15:45 UTC (History)
4 users (show)

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

Sample demonstrating the issue (12.09 KB, application/x-zip-compressed)
2016-11-04 13:30 UTC, Jerome Laban
Screenshot of the result. (106.07 KB, image/png)
2016-11-04 13:30 UTC, Jerome Laban

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 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:

Description Jerome Laban 2016-11-04 13:30:27 UTC
Created attachment 18336 [details]
Sample demonstrating the issue

Using 0.38 release and the provided sample, clicking the button should show a time consuming part of the code.

This part does not appear at all in the profiler.
Comment 1 Jerome Laban 2016-11-04 13:30:55 UTC
Created attachment 18337 [details]
Screenshot of the result.
Comment 2 Rodrigo Moya 2016-11-10 15:45:08 UTC
We have done a lot of improvements on how we process and interpret the samples we get from the runtime, so this should work much better now.

The fixes will be included in the next public release, which is coming soon.