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

Insufficient memory to continue the execution of large program. #91

Closed
jasoneue opened this issue Jan 21, 2020 · 4 comments
Closed

Insufficient memory to continue the execution of large program. #91

jasoneue opened this issue Jan 21, 2020 · 4 comments

Comments

@jasoneue
Copy link

Tried running this against a large project, and I get an Insufficient memory error. Looking at task manager, the .NET Core host process gets up to about 3GB and then fails. Computer still has plenty of memory available

log.txt

@guyacosta
Copy link
Contributor

guyacosta commented Jan 21, 2020

3GB is unusual. Have tested projects over 100MB in total size and see memory avg. around 34MB. The log error indicates a call to read one of the source files failed but I've restricted the max individual file size to 5MB to prevent long scans so I don't think it's the individual file but something else. The File.ReadAllText function indicated in the log doesn't have a set max size anyway. Was the project in a zip file of uncompressed?

@guyacosta guyacosta changed the title Insufficient memory to continue the execution of the program. Insufficient memory to continue the execution of large program. Jan 21, 2020
@guyacosta
Copy link
Contributor

If compressed, did un-compressing make a difference? We use a third party component for unzipping packages and occasionally see an issue for unknown reasons.

@guyacosta
Copy link
Contributor

No further interactions with this party nor reported cases. Closing.

@guyacosta
Copy link
Contributor

The code was adjusted thanks to a submission #104 to avoid trying to read excessively large files before we try to process them. The check was occurring too late. In addition, I now write the name of the file being processed for decompression into the log so that should help if you see it again. Let me know if not fixed now and I'll reopen this for additional investigation. Get the latest code or I'll be releasing an update of binaries asap.

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