Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Visual Studio for Mac crashes when opening Edit menu

See original GitHub issue

Every time I try to open Edit menu, Visual Studio crashes, when at least one source code file is open. (VS version 7.2 build 487, but I don’t think it matters)

It looks like the culprit is the following line: https://github.com/nosami/XSVim/blob/7.0/XSVim/XSVim.fs#L43 It was introduced in this commit: https://github.com/nosami/XSVim/commit/bb69ad6bb166691f2d7e7e4c7708c7d7e8ec5d36. If I comment out "Control+I" then the crashes do not happen.

This could be because I manually reassigned CTRL-I to “Format Document”, which is the default binding. I tried removing the binding using VS’s Preferences dialog, but still got the crashes.

Side note: I’m not convinced we should disable CTRL-I automatically. This is out-of-the-box binding to one of the most frequently used commands.

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:20 (13 by maintainers)

Top GitHub Comments

1reaction

dnlbschffcommented, Mar 1, 2018

Pretty much. The line numbers differ slightly.

System.InvalidOperationException: Invalid action command id: MonoDevelop.Ide.CodeFormatting.CodeFormattingCommands.FormatBuffer
  at MonoDevelop.Components.Commands.CommandManager.GetCommandInfo (System.Object commandId, MonoDevelop.Components.Commands.CommandTargetRoute targetRoute, System.Threading.CancellationToken cancelToken) [0x001f9] in /Users/builder/data/lanes/5402/e02ab111/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandManager.cs:1704 
  at MonoDevelop.Components.Commands.CommandManager.GetCommandInfo (System.Object commandId, MonoDevelop.Components.Commands.CommandTargetRoute targetRoute) [0x00000] in /Users/builder/data/lanes/5402/e02ab111/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Commands/CommandManager.cs:1594 
  at MonoDevelop.Components.Mac.MDMenuItem.Update (MonoDevelop.Components.Mac.MDMenu parent, System.Int32& index) [0x00014] in /Users/builder/data/lanes/5402/e02ab111/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components/Mac/MDMenuItem.cs:108 
  at MonoDevelop.Components.Mac.MDMenu.UpdateCommands () [0x00037] in /Users/builder/data/lanes/5402/e02ab111/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components/Mac/MDMenu.cs:157 
  at MonoDevelop.Components.Mac.MDSubMenuItem.Update (MonoDevelop.Components.Mac.MDMenu parent, System.Int32& index) [0x00000] in /Users/builder/data/lanes/5402/e02ab111/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components/Mac/MDSubMenuItem.cs:48 
  at MonoDevelop.Components.Mac.MDMenu.UpdateCommands () [0x00037] in /Users/builder/data/lanes/5402/e02ab111/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components/Mac/MDMenu.cs:157 
  at MonoDevelop.Components.Mac.MDMenu.MenuNeedsUpdate (AppKit.NSMenu menu) [0x00019] in /Users/builder/data/lanes/5402/e02ab111/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components/Mac/MDMenu.cs:199

(I really love the extension otherwise though!)

0reactions

nosamicommented, Mar 19, 2018

Looks like this bug was fixed in Monodevelop itself - https://github.com/mono/monodevelop/pull/4214

Should be in 7.4 service release 1.