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

Env memory leak #359

Open
xayam opened this issue May 2, 2024 · 1 comment
Open

Env memory leak #359

xayam opened this issue May 2, 2024 · 1 comment

Comments

@xayam
Copy link

xayam commented May 2, 2024

I tried to create an Environment many times using open_db and over time the RAM costs increased to the limit.

But if I alternate opening the Environment first for writing and then for reading, then the memory is freed and everything is fine

Affected Operating Systems

 Windows 11

Affected py-lmdb Version

lmdb 1.4.1
@jnwatson
Copy link
Owner

Do you have any example code?

Keep in mind that OSs are not very transparent at reporting mapped memory without using alternative tools. It will report mapped memory as in use where in reality is it just using up virtual memory space of the process, which is essentially free.

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