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

Lock memory map when reading from file #234

Merged
merged 5 commits into from
Jan 5, 2024
Merged

Conversation

arkpar
Copy link
Member

@arkpar arkpar commented Jan 5, 2024

Closes #233

Copy link
Collaborator

@cheme cheme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sense.
I remember having issues testing the grow method of windows on a linux and my code at the time was droping before creating but I think it solve nothing in this case the lock looks needed.
Just wondering if the lock is stricly linux when using linux grow method (overall seems safer to have it)?

@nazar-pc
Copy link
Contributor

nazar-pc commented Jan 5, 2024

I'll run it for longer, but memory usage on Windows with this patch looks very promising so far

@nazar-pc
Copy link
Contributor

nazar-pc commented Jan 5, 2024

I have a high degree of confidence this fixes #233. Previously in less than an hour it was crashing, now I don't see any indication of the problem happening at all.

Would be awesome to get this in a patch version.

@arkpar arkpar merged commit 8b5dba8 into master Jan 5, 2024
9 checks passed
@arkpar arkpar deleted the arkpar/locked-slice branch January 5, 2024 13:06
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

Successfully merging this pull request may close these issues.

Memory is "leaking" on Windows and leads to crashes
3 participants