Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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.
@Rodrigo, Could you please add more Steps or Screencast to reproduce this issue, so that I can confirm this issue at our end.
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
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.
And I am able to reproduce this issue with previous profiler build i.e 32.99.124.
@asim @rodrigo can we resolve it as NOT_REPRODUCIBLE/FIXED?
Yes, we no longer drill down to stacktraces anymore, so this shouldn't happen anymore, so closing