Bug 15157 - XS reaches and 100% CPU usage and hangs on Windows
Summary: XS reaches and 100% CPU usage and hangs on Windows
Status: RESOLVED DUPLICATE of bug 15596
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.12
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-10-03 02:48 UTC by Prashant Cholachagudda
Modified: 2013-11-17 18:52 UTC (History)
2 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 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:

Description Prashant Cholachagudda 2013-10-03 02:48:23 UTC
XS reaches and 100% CPU usage and hangs after using few minutes.
When Text Editor's Behaviour Setting is "Use Vi modes".

Steps to reproduce:
Have a Solution (lets call it "A") with multiple files open.
Goto Tools -> Options -> Text Editor -> Behaviour
Check "Use Vi mode" option.
Close XS.
Open XS.
Open File -> Recent Solutions -> A

Then what happens:
XS loads the Solution. While trying to display the files content it 
enters a single threaded busy loop and XS remains totally unresponsive.

Additional indication:
Disabling the 'Vi modes' prior to loading A lets XS open solution A just 
Comment 2 Mikayla Hutchinson [MSFT] 2013-10-03 14:41:04 UTC
I cannot reproduce this. Do you have VS installed to attach and get a stack trace of the main thread?
Comment 3 Ronnie Holm 2013-11-17 17:55:15 UTC
Stack trace information for the issue is here:

Comment 4 Mikayla Hutchinson [MSFT] 2013-11-17 18:52:29 UTC
Comment 5 Mikayla Hutchinson [MSFT] 2013-11-17 18:52:35 UTC

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