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.
On launching Xamarin Game Studio 4.0.5, the CPU usage is approx. 20% (one 100% on a CPU core) and the memory usage keeps climbing (last noted at 800MB+)
Launch Xamarin Game Studio.
Updated to 4.0.5 when notified.
Restarted Xamarin Game Studio automatically.
Loaded solution that was fine before update.
Notice task manager usage.
Should be idle and use far less memory.
Repro. 100% after loading a solution.
Xamarin Studio performs background analysis of the source files and referenced assemblies, so the behavior you describe is normal until all information has been cached.
Does the CPU keep running 100% after a few minutes of opening the project?
It does take some time to settle down. The reason I noticed it was that my laptop will ramp up the fans when CPU is above 10% and was the first time I noticed this behaviour.
After it settles down, if you close Xamarin Studio, reopen it and reopen the solution, do you consistently get the same high CPU usage, for the same time?
It's quicker and settles down within a few seconds. It was the first time the solution was opened with the update. Is this feature new to this update?
No, but we only regenerate the cached information after an update that requires the caches to be invalidated for some reason, for example, cache format changes.
If it weren't for the caches, this would happen every time :)
This bug was marked as fixed for Xamarin Studio 4.0.9, which is currently in the beta channel. Try it out!