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 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.
Created attachment 13209 [details]
Logs from my repo of the issue
From this enterprise desk case:
Related to this bug report filed by the same customer:
"Xamarin.Android call performance is 4 times slower on inherited views"
## Customer Message describing the issue
"...this is an extension of the bug 32126, which states that the call performance is 4x slower for inherited views. The 4x slower stated in the bug was related to inherited view creation. When related to method calls, its 13x slower on a Nexus 5 (on Android 5.0)"
## Steps to reproduce the issue
I was able to reproduce the issue as follows:
1. Build & deploy the app
2. Tap the button
3. The performance values are shown by the app.
## Expected results
The values shown should be the same or generally close, and fast. (Since this is a performance question, it's tricky to describe the "expected" behavior, but the differences are noticeable.)
## Actual results
In my tests with an LG Volt API 19, I noticed the "non-threshold" test was around 3-4x slower than the "threshold" test.
The customer reports that their Nexus 5 (on Android 5.0) is around 13x slower.
Since I still noticed a discrepancy, I think it's still reasonable to consider this "confirmed" but it seems possible some devices might be hitting this to a more extreme degree than in my tests.
## Build information
=== Xamarin Studio ===
Version 5.9.7 (build 9)
Installation UUID: 8ef63a7c-1b18-40de-a334-7f78777fcb55
Mono 4.0.4 ((detached/d481017)
GTK+ 2.24.23 (Raleigh theme)
Package version: 400040004
=== Apple Developer Tools ===
Xcode 7.0.1 (8228)
=== Xamarin.iOS ===
Version: 220.127.116.11 (Business Edition)
Build date: 2015-09-18 23:22:05-0400
=== Xamarin.Android ===
Version: 18.104.22.168 (Business Edition)
Android SDK: /Users/kentgreen/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.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
5.1 (API level 22)
Java SDK: /usr
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
=== Xamarin Android Player ===
Version: Unknown version
Location: /Applications/Xamarin Android Player.app
=== Xamarin.Mac ===
Version: 22.214.171.124 (Business Edition)
=== Build Information ===
Release ID: 509070009
Git revision: 31fa64709030b3edb971237780a452a4c69943c4
Build date: 2015-09-17 11:44:37-04
Xamarin addins: b105d33d8cd72911ff2cf3ee0b7715d37e5f19a6
=== Operating System ===
Mac OS X 10.10.5
Darwin Kents-Macbook-Pro.local 14.5.0 Darwin Kernel Version 14.5.0
Wed Jul 29 02:26:53 PDT 2015
## Additional notes
Adding sample as a private attachment, since it was provided by the customer. Adding IDE logs from my reproduction of the issue.
*** This bug has been marked as a duplicate of bug 32126 ***