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

Crash when copying large amounts of data to clipboard #5498

Closed
djpereira opened this issue Apr 19, 2016 · 2 comments
Closed

Crash when copying large amounts of data to clipboard #5498

djpereira opened this issue Apr 19, 2016 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues

Comments

@djpereira
Copy link

  • VSCode Version: 1.0.0
  • OS Version: Windows 10 v1511

Steps to Reproduce:

  1. Open a large file (35MB or more).
  2. Select All (Ctrl+A)
  3. Copy to clipboard (Ctrl+C)

The file opens and you can navigate very quickly. That works great, but trying to copy the whole file to clipboard makes the app crash. I am not sure there are any logs that I can pull to help diagnose the problem.

image

@dbaeumer dbaeumer added the bug Issue identified by VS Code Team member as probable bug label Apr 19, 2016
@alexdima
Copy link
Member

I think it is an OOM crash. I don't think we do anything stupid on Ctrl+C:

  • we create a big fat JS string with all the text
  • we call event.clipboardData.setData('text/plain', text);

Most likely this crashes when creating the big fat JS string with all the text.

@alexdima alexdima added the freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues label Apr 28, 2016
@alexdima
Copy link
Member

alexdima commented Mar 1, 2017

I have taken the following 4MB file and copy-pasted it 12 times until I got a file that is 50MB:

editor.main.zip

I then opened that file in vs code and successfully did ctrl+a and ctrl+c and had the text in the clipboard. I pasted it in a different instance of VS Code. The renderer process consumes 430MB for me in this case.

This OOM can be avoided if we would ship a 64 bit version on Windows. #21640

@alexdima alexdima closed this as completed Mar 1, 2017
@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 freeze-slow-crash-leak VS Code crashing, performance, freeze and memory leak issues
Projects
None yet
Development

No branches or pull requests

3 participants