Bug 16637 - BookmarkXamarin Studio hangs when opening most .cs code windows
Summary: BookmarkXamarin Studio hangs when opening most .cs code windows
Status: RESOLVED DUPLICATE of bug 15596
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.2.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-12-06 02:03 UTC by Nicola Iarocci
Modified: 2013-12-06 14:20 UTC (History)
1 user (show)

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


Attachments
Log files (7.61 KB, application/zip)
2013-12-06 02:06 UTC, Nicola Iarocci
Details


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 15596

Description Nicola Iarocci 2013-12-06 02:03:48 UTC
Step to reproduce:

- Open a solution
- Double click on a CS file which is now opened in the code editor yet
- Enjoy beachball of death.

XS 4.3.0 build 52 (alpha) on Mavericks. Any help appreciated as I'm literally stuck now.
Comment 1 Nicola Iarocci 2013-12-06 02:06:24 UTC
Created attachment 5615 [details]
Log files
Comment 2 Mikayla Hutchinson [MSFT] 2013-12-06 14:20:47 UTC
This is a bug in the vi mode, you can work around it by disabling vi mode.

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