Bug 46471 - Stack frames are inverted
Summary: Stack frames are inverted
Status: RESOLVED FIXED
Alias: None
Product: Profiler
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jose Miguel Torres
URL:
: 46464 ()
Depends on:
Blocks:
 
Reported: 2016-11-04 14:00 UTC by Jerome Laban
Modified: 2016-11-04 18:53 UTC (History)
4 users (show)

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


Attachments
Screenshot of the result. (110.01 KB, image/png)
2016-11-04 14:00 UTC, Jerome Laban
Details


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:
Status:
RESOLVED FIXED

Description Jerome Laban 2016-11-04 14:00:07 UTC
Created attachment 18340 [details]
Screenshot of the result.

Using version 0.38, and a simple sample application, the attached frames are displayed inverted by default.

On a related note, seen in the attached screen shot, this shows that JNINativeWrapper calls Guid.NewGuid, which is definitely not a good way to have a performant unique ID.
Comment 1 Rodrigo Moya 2016-11-04 18:44:30 UTC
Right, we noticed and fixed this one already, should be in the next update, hopefully next week.
Comment 2 Rodrigo Moya 2016-11-04 18:53:02 UTC
*** Bug 46464 has been marked as a duplicate of this bug. ***