Bug 39610 - Drilling down to empty stacktraces
Summary: Drilling down to empty stacktraces
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Profiler
Classification: Xamarin
Component: General ()
Version: 0.32.x
Hardware: PC All
: High major
Target Milestone: (C8)
Assignee: Jose Miguel Torres
URL:
Depends on:
Blocks:
 
Reported: 2016-03-14 18:52 UTC by Rodrigo Moya
Modified: 2016-08-08 11:14 UTC (History)
5 users (show)

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

Description Rodrigo Moya 2016-03-14 18:52:21 UTC
Some classes (OutOfMemoryException allocated at startup by the runtime) have no associated stack trace, so when drilling down to them, a list with an empty method is displayed as the only data in the list, which is confusing, so we should probably avoid drilling down in those cases.
Comment 1 asimk 2016-06-30 17:07:21 UTC
@Rodrigo, Could you please add more Steps or Screencast to reproduce this issue, so that I can confirm this issue at our end.
Comment 2 Rodrigo Moya 2016-07-04 09:55:10 UTC
Yes:

1. Group allocations summary by method (for System.String for instance)
2. Sort by caller and see if there is a row with an empty value for the 'Caller' column
3. Double click on it to see the allocations for that group

Before the allocations summary+list merge, this was just displaying a list of allocations without a stacktrace, but now, it even crashes
Comment 3 asimk 2016-07-21 17:09:55 UTC
I have checked this issue with the help of steps provided in comment 2 but I am not getting any empty value for the caller column with latest build i.e. 0.34.0.
Screencast: http://www.screencast.com/t/YCTYUP5xkBxJ

And I am able to reproduce this issue with previous profiler build i.e 32.99.124.
Screencast: http://www.screencast.com/t/WcafQdud
Comment 4 Oleg Demchenko 2016-08-03 18:50:52 UTC
@asim @rodrigo can we resolve it as NOT_REPRODUCIBLE/FIXED?
Comment 5 Rodrigo Moya 2016-08-08 11:14:48 UTC
Yes, we no longer drill down to stacktraces anymore, so this shouldn't happen anymore, so closing