Bug 17868 - mtbserver uses too much CPU
Summary: mtbserver uses too much CPU
Status: RESOLVED DUPLICATE of bug 13691
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.12.x
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: 1.12 (Merge)
Assignee: Vinicius Jarina
Depends on:
Reported: 2014-02-19 02:20 UTC by Rainer Mager
Modified: 2015-01-05 11:20 UTC (History)
8 users (show)

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

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 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 Rainer Mager 2014-02-19 02:20:41 UTC
Pairing with the build host is fine normally, but if I shut down my PC then the mtbserver process on my Mac starts using 100% CPU of 1-core. I can reproduce this reliably.

I don't know if it matters, but I'm actually using VMWare for my PC, and I'm suspending that Windows virtual machine.
Comment 1 Justin Caldicott 2014-03-21 09:45:59 UTC
I'm the same issue with mtbserver using 100% CPU, though this is even with the PC and visual studio still running.  No builds have been running for a couple of hours.

For now, I'll just have to turn on the build helper when needed, as my poor mac mini was getting very hot!
Comment 2 Dominique Louis 2014-03-21 09:59:23 UTC
A Fix for this is due on in the 1.12 release. It should be passed to the QA team very soon.
Comment 3 Justin Caldicott 2014-03-21 10:11:50 UTC
Thanks for the prompt update Dominique!
Comment 4 Vinicius Jarina 2014-03-27 10:48:49 UTC
Dup of 13691

*** This bug has been marked as a duplicate of bug 13691 ***