Bug 47171 - [Profiler Mac] Path to roots is empty
Summary: [Profiler Mac] Path to roots is empty
Alias: None
Product: Profiler
Classification: Xamarin
Component: Mac ()
Version: 0.38.x
Hardware: PC Mac OS
: High normal
Target Milestone: (C9)
Assignee: Rodrigo Moya
Depends on:
Reported: 2016-11-17 13:34 UTC by Jean-Marie Gueirard
Modified: 2017-08-01 18:42 UTC (History)
5 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 Jean-Marie Gueirard 2016-11-17 13:34:24 UTC
We are currently facing an issue with the Profiler, the path to root for live objects is always empty.

I followed the procedure described here, but it didn't help : https://forums.xamarin.com/discussion/80740/reference-tree-is-empty 

http://sky.qxlricardo.com/owncloud/index.php/s/HMybXk3mAPuH891 (with the USB connect timeout)

I'm not sure if it's a duplicate from https://bugzilla.xamarin.com/show_bug.cgi?id=45320

Xamarin Studio Enterprise
Version 6.1.2 (build 44)
Installation UUID: d4727170-b3f6-4abf-8255-65494233c738
	Mono 4.6.2 (mono-4.6.0-branch/08fd525) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 406020007


Version: 0.38.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

Version: (Xamarin Enterprise)
Android SDK: /Developer/android-sdk-macosx
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)
		7.0    (API level 24)

SDK Tools Version: 25.1.6
SDK Platform Tools Version: 22.0.0
SDK Build Tools Version: 23.0.0

Java SDK: /Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)

Android Designer EPL code available here:

Xamarin Android Player
Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

Apple Developer Tools
Xcode 8.1 (11544)
Build 8B62

Version: (Xamarin Enterprise)
Hash: 44931ae
Branch: xcode8.1
Build date: 2016-11-01 20:52:28-0400

Not Installed

Xamarin Inspector
Hash: e931a52
Branch: master
Build date: Thu, 18 Aug 2016 17:46:46 GMT

Build Information
Release ID: 601020044
Git revision: 0ccfcd52b95305ebd5b7eca0d88c1017035910ae
Build date: 2016-10-28 15:12:43-04
Xamarin addins: a39a869d8a78d87bdc6775f696c13a4cc9024501
Build lane: monodevelop-lion-cycle8

Operating System
Mac OS X 10.11.6
Darwin JymMacMici.local 15.6.0 Darwin Kernel Version 15.6.0
    Thu Sep  1 15:01:16 PDT 2016
    root:xnu-3248.60.11~2/RELEASE_X86_64 x86_64
Comment 1 asimk 2016-11-18 14:06:40 UTC
@Jean-Marie Gueirard, I have checked this issue with profiler version and 1.0.1-2 and unable to reproduce this issue.
Screencast: http://www.screencast.com/t/Da7R3d1Y72

Please review the screencast and let me know what additional steps we need to follow to reproduce this issue.

Comment 2 Rodrigo Moya 2016-11-20 12:59:37 UTC
While the app is being profiled, paths to roots is not available, it's only when you're done processing, as it needs to generate the whole references tree, which is time consuming, and hence is only done once at the end of the profling session.

So, are you not seeing any paths to roots to any object when the app is finished?
Comment 3 Jean-Marie Gueirard 2016-11-21 08:14:26 UTC
Thanks to @asimk screencast, I just find out that we were missing a step. We were looking at the All allocations tab, without double clicking on an object.
Comment 4 asimk 2016-11-21 11:27:10 UTC
Marking as verified with reference to comment 2 and comment 3.
Comment 5 Chris Dinon 2017-08-01 18:42:55 UTC
I was able to observe Paths to Root after ending profiling. However, the profiler doesn't indicate anywhere that Paths to Root isn't populated until after testing. This is hidden knowledge and should be shared to the user if it's intended.