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.
I updated to 3.9.236 today. I started immediately having a java.exe process spawned every second or two taking from 30 to 90 % of my CPU and then dying. I cannot work this way so I am forced to downgrade to your previous version.
Windows 7 64-bit
Visual Studio 2013 Update 4
Java: I had the 1.8 64-bit run-time. Thinking that could be the problem, I uninstalled it. It didn't help, it started spawning the 1.7 64-bit one. I removed that too for the same result, it started doing it with the 1.8 64-bit JDK. I removed that too, it just started using the 1.7 64-bit JDK. Obviously I cannot remove the last one because Android wouldn't work.
Sorry, I didn't clarify how exactly it happens. One needs to just open his Monodroid solution, nothing else. No building, no editing, just staying open causes the process to constantly appear and die.
Has anyone been able to reproduce this?
Please comment on this, it forces me to keep using an old version.
Absolutely the same happens with 3.9.289.0. When will you fix it or at least reply?
Thanks for the report! There is a candidate fix under testing now. If all goes smoothly, the fix will be published in alpha/beta builds sometime within the next few weeks.
I'll mark this bug as a duplicate of another bug on this issue. That bug by chance ended up being the main point for tracking the bug. It also includes a link to a forum announcement that discusses a possible temporary workaround.
*** This bug has been marked as a duplicate of bug 26122 ***