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

QuickLook takes a huge memory when previewing a txt file #1223

Open
sharpchen opened this issue Nov 25, 2022 · 3 comments
Open

QuickLook takes a huge memory when previewing a txt file #1223

sharpchen opened this issue Nov 25, 2022 · 3 comments

Comments

@sharpchen
Copy link

sharpchen commented Nov 25, 2022

Describe the bug
Same as title

To Reproduce
Steps to reproduce the behavior:

  1. Previewing a txt file, its size is about 64KB. It's a metadata file of a landsat image.
  2. Scroll down, then the program freeze.
  3. Go to monitor, it took about 6600MB of memory as displayed

Desktop (please complete the following information):

  • OS Version: [Windows 10 21H2]
  • QuickLook Version: [v3.7.3 UWP from Windows Store]

Screenshots and Exception Log

bandicam 2022-11-25 15-03-08-351 00_00_00-00_00_30

Last line of this text is as the picture showed, it's gray colored, doesn't like normal content.
I have no idea what it is.
It just duplicates <0x00> for many times and I can't even copy the content.

Snipaste_2022-11-25_15-32-08

I've checked the log, no exception recorded for this issue.

@xupefei
Copy link
Member

xupefei commented Nov 28, 2022

Mind uploading the file to this issue?

@sharpchen
Copy link
Author

Mind uploading the file to this issue?
L71119042_04220010304_MTL.txt

@xupefei
Copy link
Member

xupefei commented Nov 29, 2022

This file do have A LOT of NULLs at the end:
image

The number of NULLs are so many such that it hit the performance limit of AvalonEdit: icsharpcode/AvalonEdit#376. I consider this an upstream issue.

Back to your problem - I suggest to investigate which application produced those NULLs at the end of the file. I saw those "filling bytes" in binary files, but never in plain texts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants