Bug 14945 - Xamarin Studio uses 100% CPU
Summary: Xamarin Studio uses 100% CPU
Status: RESOLVED DUPLICATE of bug 14912
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.1.11
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-09-23 21:14 UTC by Frank A. Krueger
Modified: 2013-09-24 04:04 UTC (History)
1 user (show)

Tags:
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 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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 14912

Description Frank A. Krueger 2013-09-23 21:14:11 UTC
Description of Problem:

Xamarin Studio 4.1.11 (build 10) always uses 100% CPU.

Steps to reproduce the problem:
1. Run XS


Actual Results:

100% CPU

Expected Results:

0% CPU

How often does this happen? 

Always

Additional Information:

Seems to be a bug with just the .11 release.

Xamarin Studio
Version 4.1.11 (build 10)
Installation UUID: d42ff219-94da-4f6f-b191-60ec5a46a217
Runtime:
	Mono 3.2.3 ((no/8d3b4b7)
	GTK+ 2.24.20 theme: Raleigh
	GTK# (2.12.0.0)
	Package version: 302030000
Comment 1 Mikayla Hutchinson [MSFT] 2013-09-24 04:04:29 UTC

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