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.
When I compile with arm64-v8a and deploy to a Hardware capable of running 64bit instruction set, I get the following problems where there will be tens of getprop zombie process. It will go away if the application is killed. However, I do not have any issue with the other "Android Options".
1) Create an empty Android project
2) Go to Project -> properties -> Android Options -> Advanced then tick only arm64-v8a
3) Compile and deploy (does not matter if it is Debug or Release).
4) Go to Tools -> Android -> Andriod adb command prompt
5) c:> adb shell
6) ps | grep getprop
HW: Xiaomi Redmi 3S
OS: Andriod MarshMallow 6.0.1
Visual Studio 2015 V14.0.25421.03 Update 3
Android API 23
I attempted to reproduce this by deploying to a Google Pixel which is arm64-v8a:
Unfortunately, I do not see any zombie processes with this device running a sample app with the arm64-v8a architecture only. Running the "ps" (process list) command and grepping for "getprop" yields 0 results.
Can you potentially provide a video, screenshot, or text snippet of the processes that you are seeing?
Thus I am marking this issue as NEEDINFO for the time being.
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!