You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FastGotToFile has been great for months in VS 2019 but has started causing VS to hang as soon as it is invoked with Ctrl-Alt-F (mapped to Tools.FastGoToFile), in VS v. 16.4.4 (and 16.4.3 or 16.4.2). I am forced to close VS in Task Manager, where it has spawned many sub-processes (console window host, ServiceHub.Host.CLR.x86..., etc.). Let me know if I can provide more info.
The text was updated successfully, but these errors were encountered:
Sorry to hear that it's not working for you anymore. I have run basically every version of VS 2019 and had no problems, so this doesn't seem 100% reproducible. It is possible that it's trying to browse some broken or huge location by default when you open it which would basically hang.
A few things:
You can try removing the registry entries to force it to go back to a default mode. Just delete the registry key at 'HKEY_CURRENT_USER\Software\GalenElias\FastGoToFile'. This would be an easy thing to try with little downside and might very well clear up the issue. It would be interesting to save off a screenshot of your settings before trying in case it does fix the issue I'd be curious to know what values were causing the issue.
A callstack/dump of Devenv.exe would be ultimately needed to actually figure out what's going on, although might be quite large for the Visual Studio process. These can be created from Task Manager by right clicking on the process and selecting 'Create Dump File'.
FastGotToFile has been great for months in VS 2019 but has started causing VS to hang as soon as it is invoked with Ctrl-Alt-F (mapped to Tools.FastGoToFile), in VS v. 16.4.4 (and 16.4.3 or 16.4.2). I am forced to close VS in Task Manager, where it has spawned many sub-processes (console window host, ServiceHub.Host.CLR.x86..., etc.). Let me know if I can provide more info.
The text was updated successfully, but these errors were encountered: