Bug 27393 - Snapshot 0 is showing changes from snapshot 3
Summary: Snapshot 0 is showing changes from snapshot 3
Alias: None
Product: Profiler
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Rodrigo Moya
Depends on:
Reported: 2015-02-25 05:01 UTC by Rudolf Fäder
Modified: 2015-06-29 05:33 UTC (History)
3 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 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 Rudolf Fäder 2015-02-25 05:01:30 UTC
I am taking 5 snapshots profiling an iOS application based on Mono. When I take a look in Snapshot 0 under byte[], it shows an instance recorded with snapshot 2 or 3. This I can tell from looking at the timestamp of the particular instance. So either this entry is wrong in Snapshot 0 or the timestamp is not correct.
Comment 1 Rodrigo Moya 2015-02-25 09:53:02 UTC
Yes, known problem, as should be already fixed in our internal builds. So, closing this, but as soon as you get a new preview release (with version number > 0.11.0, which is the latest we have published), please feel free to re-open if it still happens to you.
Comment 2 Udham Singh 2015-06-29 05:33:58 UTC
Hi @Rudolf,

Could you please check this issue with latest profiler build 0.17 and let us know if you are still getting this issue. You can get latest profiler build from link https://xamarin.com/profiler