Bug 33863 - Static Registrar is still showing dynamic registrar while profiling
Summary: Static Registrar is still showing dynamic registrar while profiling
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: XI 8.10
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on: 56022
  Show dependency tree
Reported: 2015-09-10 17:31 UTC by John Miller [MSFT]
Modified: 2018-03-09 14:37 UTC (History)
3 users (show)

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

Profiler Log (311.10 KB, application/zip)
2015-09-10 17:31 UTC, John Miller [MSFT]

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 or GitHub 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 John Miller [MSFT] 2015-09-10 17:31:39 UTC
Created attachment 12859 [details]
Profiler Log


   While profiling an app with the --registrar:static mtouch option, dynamic registrar calls are still showing up while profiling. 

**Steps to Reproduce:**

   1. Create a new Single View iOS app. 
   2. Add the --registrar:static to the Additional mtouch args in the iOS Build project options menu. 
   3. Go to Run -> Start Profiling (simulator build)

**Actual Results:**

   There are DynamicRegistrar traces in the profiling information. http://screencast.com/t/cKNpoeAOlm
   Attached is the Xamarin profiler log. 

**Expected Results:**

   No dynamic registrar information. 

**Build Date & Platform:**

   === Xamarin Studio ===

Version 5.9.5 (build 10)
Installation UUID: e01c3049-a2d2-4e0a-aad8-afe6fb627c4d
	Mono 4.0.3 ((detached/d6946b4)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400030020

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/johnmiller/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.4   (API level 19)
		5.0   (API level 21)
		5.1   (API level 22)
Java SDK: /usr
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Apple Developer Tools ===

Xcode 6.4 (7720)
Build 6E35b

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 2c66d2f
Branch: master
Build date: 2015-08-04 13:52:25-0400

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 509050010
Git revision: 48d16bc4f12ce3938964fc7c3d72fdc6887ad4ad
Build date: 2015-08-18 16:55:24-04
Xamarin addins: c2d51b360ad9f59e689046d47030df27de28f94a

=== Operating System ===

Mac OS X 10.10.2
Darwin Johns-Work-MacBook-Pro.local 14.1.0 Darwin Kernel Version 14.1.0
    Thu Feb 26 19:26:47 PST 2015
    root:xnu-2782.10.73~1/RELEASE_X86_64 x86_64
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-09-11 04:03:03 UTC
There will always be a dynamic registrar at runtime, because it's technically possible (we have the API, but it's not used much), to register methods during execution (and we need the dynamic registrar for this).

In any case I'll have a look and see if there's something unexpected going on.
Comment 2 Sebastien Pouliot 2017-05-15 19:01:41 UTC
*** Bug 56022 has been marked as a duplicate of this bug. ***
Comment 3 Rolf Bjarne Kvinge [MSFT] 2018-03-09 14:37:29 UTC
This was fixed with the fix for bug #56022.