Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception when close all working files and some are dirty #4253

Closed
isidorn opened this issue Mar 15, 2016 · 17 comments
Closed

Exception when close all working files and some are dirty #4253

isidorn opened this issue Mar 15, 2016 · 17 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented Mar 15, 2016

  • VSCode Version: 18ebb4a
  • OS Version: any

Steps to Reproduce:

  1. Have multiple files open in working files
  2. Have at lease one of those files dirty
  3. Close All Working files by clicking the close action in the working files header, notice the exception
  4. I can not repro this every time, but see it regularly

screen shot 2016-03-15 at 15 19 34

edited: first exception that I now removed was caused by an unrelated issue

@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Mar 15, 2016
@bpasero
Copy link
Member

bpasero commented Mar 15, 2016

@isidorn do you get the dialog prompting you to save dirty files before the exception or after?

@bpasero bpasero added the important Issue identified as high-priority label Mar 15, 2016
@bpasero bpasero added this to the March 2016 milestone Mar 15, 2016
@isidorn
Copy link
Contributor Author

isidorn commented Mar 15, 2016

I get the dialog and I say 'do not save' - can not always repro, can you please try it out a couple of times

@bpasero bpasero assigned jrieken and unassigned bpasero Mar 15, 2016
@bpasero
Copy link
Member

bpasero commented Mar 15, 2016

I dont even know what that handler is as it seems in the extension host, moving to @jrieken / @alexandrudima

@alexdima
Copy link
Member

@isidorn Can you reproduce without installed extensions?
Hint: "Notification handler" string is not in vscode source code.

@isidorn
Copy link
Contributor Author

isidorn commented Mar 15, 2016

@alexandrudima I can repro it if I do not have any extensions installed

@jrieken jrieken assigned isidorn and unassigned jrieken Mar 15, 2016
@jrieken
Copy link
Member

jrieken commented Mar 15, 2016

@isidorn The steps don't do it for me, also the message appears nowhere in our sources. Please attach the debugger to the extension host and break on error such that we have a chance to understand this

@alexdima
Copy link
Member

@dbaeumer Maybe you use such strings in the language protocol?

@isidorn
Copy link
Contributor Author

isidorn commented Mar 15, 2016

@jrieken when I attach debugger to the extension host I can not seem to get it to break on this error.
I can easily repro so just drop by my table if you are interested in looking into this.

@isidorn isidorn assigned jrieken and unassigned isidorn Mar 15, 2016
@jrieken
Copy link
Member

jrieken commented Mar 15, 2016

@isidorn
Copy link
Contributor Author

isidorn commented Mar 15, 2016

@jrieken I do not have powershell installed

@jrieken
Copy link
Member

jrieken commented Mar 15, 2016

maybe tslint?

@isidorn
Copy link
Contributor Author

isidorn commented Mar 15, 2016

I do not have any extensions installed :)
I only use open in github but I uninstalled it to try to repro this issue, and I could repro

@jrieken
Copy link
Member

jrieken commented Mar 16, 2016

Yes you have. It's called JSON and uses the language server protocol. Moving to @dbaeumer cos this seems to come from /Users/jrieken/Code/vscode/extensions/json/server/node_modules/vscode-languageserver/lib/protocol.js

@jrieken jrieken assigned dbaeumer and unassigned jrieken Mar 16, 2016
@dbaeumer
Copy link
Member

The protocol calls a notification handler which causes an exception. The protocol on the lowest level catches the excpetion sends it back to the client which prints it to the console. There is nothing I can do better. The root cause of the exception must be fixed.

The root cause lies in the languge server. I receive an update event for a document that is already closed. The interesting question is why? But I will protect my code against it.

@dbaeumer
Copy link
Member

This issue was moved to microsoft/vscode-languageserver-node#28

@dbaeumer
Copy link
Member

Published 1.4.1 of the language server.

@dbaeumer dbaeumer assigned isidorn and unassigned dbaeumer Mar 21, 2016
@isidorn isidorn added the verified Verification succeeded label Mar 23, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants