Bug 3485 - MonoDevelop hangs (takes 100% CPU) due to code completion popup
Summary: MonoDevelop hangs (takes 100% CPU) due to code completion popup
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 2.8.6
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-02-15 15:37 UTC by Kristian Rietveld (inactive)
Modified: 2012-02-16 04:40 UTC (History)
1 user (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 Kristian Rietveld (inactive) 2012-02-15 15:37:53 UTC
Steps to reproduce:

  1. Launch MonoDevelop and have a project opened.
  2. Make sure a C# file is active in the text editor.
  3. Move the MonoDevelop window past the left edge of the screen, such that half of the text editor is no longer visible.
  4. Make sure the cursor is not visible (so it is in the part of the text editor which is no longer visible on the screen).
  5. Start typing something that triggers code completion like "Console.W".
  6. Code completion should pop up.
  7. MonoDevelop now hangs and takes 100% CPU.

It looks like MonoDevelop uses 100% CPU because the process is repeatedly running a timeout handler (implemented in C# since symbols are not visible in gdb) which frequently calls gtk_window_get_position().  Could this be the code completion popup positioning function going awry?
Comment 1 Mike Krüger 2012-02-16 04:40:19 UTC