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

Extremely large files display error "Open a file to toggle bookmarks" #31

Closed
adamzl opened this issue Aug 16, 2016 · 5 comments
Closed
Assignees
Labels
bug caused by vscode The issue was caused by a VS Code update wontfix

Comments

@adamzl
Copy link

adamzl commented Aug 16, 2016

When attempting to use any of the bookmark commands on a very large file (100,000 lines anecdotally) an info popup appears at the top displaying the message: "Open a file first to toggle bookmarks".

My reproduction:

  1. Open large file.
  2. Attempt to toggle breakpoint
  3. Failure message appears.
  4. Create copy of the large file.
  5. Cut the file down to 50 lines.
  6. Save, close, reopen pruned copy.
  7. Can now toggle breakpoints.
@alefragnani
Copy link
Owner

Hi @adamzl ,

I could reproduce the problem 👍 .

There seems to be an issue in VSCode core that erroneously says that there is no ActiveText. Unfortunatelly there is no workaround for that and I will have to report the problem to VSCode team, and wait for and alternative/solution, to have this fixed in the extension.

Thanks for repoting.

@alefragnani alefragnani self-assigned this Aug 16, 2016
@alefragnani
Copy link
Owner

It seems, based on this VSCode issue, that this is by design, and large files will be invisible to extensions.

Being so, there is no way to fix it, neither a workaround.

Sorry about that.

@adamzl
Copy link
Author

adamzl commented Aug 23, 2016

No worries, I'll always have Visual Studio for those monster-beast files.

@aplatypus
Copy link

I have previously reported this System Failure and there are now many related issue reports al falling back to the Same Root Cause ...

  • VS Code wants to have all the file in memory

We deal with very large text files when dealing with production problems. We have large data dumps, large log file sets, text based transaction snapshots and HTTP traffic, etc, etc.

It is essential that we have an edit tool that Can handle files as large a the (disk) storage capacity. This is not some "new science", editors that can work on files bigger than memory have been around a very long time.

What is most alarming is that a great many issues related to this are closed-off so there can be no input from end-users. It is well that I don't have a tin-foil hat.

@alefragnani
Copy link
Owner

Hi @aplatypus ,

The VS Code limitation still remains today. I understand your point, and I agree that "it should work", but I can't do anything about it. So, I suggest you to upvote/comment on VS Code repo issues that talks about it.

I found at least 3:

The good point is, when VS Code fixes this issue, I probably don't have to do anything on my side.

Repository owner locked as resolved and limited conversation to collaborators May 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug caused by vscode The issue was caused by a VS Code update wontfix
Projects
None yet
Development

No branches or pull requests

3 participants