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

Bug: Potential memory leak - "out of memory situation" #41

Open
aurbus opened this issue Aug 16, 2024 · 3 comments
Open

Bug: Potential memory leak - "out of memory situation" #41

aurbus opened this issue Aug 16, 2024 · 3 comments

Comments

@aurbus
Copy link

aurbus commented Aug 16, 2024

I was recently processing some images in Scantailor and the program crashed and showed an "out of memory situation" dialog (telling me to use the 64 bit version, but I already am). I updated to the latest release, and I had the same issue. I should note I am using the "0.2024.08.15-X86-64" release.

I looked through Windows Event Viewer, and did not see any logs to speak of. I have attached a few of the images I was processing at the time. Please let me know if there is any other information I can provide that might be of use.

I am running a Dell XPS 13 9310 2-in-1 with Tiny11 (Windows 11 22621.2283)

pic 079
pic 142
pic 151

@plzombie
Copy link
Contributor

Hi @aurbus . Scantailor processes images as 32bit, so it took 55MB to just load image. On your 3 images I have about 250MB usage with 1gb peak memory usage. Have you opt in increase resolution flag in Output section? Can you also tell me your amount of free virtual memory (and swap file size)?

@aurbus
Copy link
Author

aurbus commented Aug 17, 2024

Ah ok, that makes sense about the 32 bit processing. These images were scanned at 2400DPI, as I want the output PDF to be as nice as possible.

This happened during the processing (content selection), so I had not yet gotten to the output stage (and even then I was not planning on selecting any resolution enhancement)

When running the content selection (and all previous steps) Scantailor is using about 5GB of RAM, with the system overall hovering around 80-85% usage.

I'm not sure exactly how to check swap file size in Windows (I'm generally using Debian) but SystemPropertiesPerformance.exe tells me 5.3GB for the paging file size.

@plzombie
Copy link
Contributor

@aurbus can you tell me amount of scans you process?

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