nervmor

> hello! > > Please, do you have any news on this issue? I tested in two different environments in **java 8 + duckdb 0.10.0 + windows** and in **java...

> > > hello! > > > Please, do you have any news on this issue? I tested in two different environments in **java 8 + duckdb 0.10.0 + windows**...

@brianwyka You should close the database object after all thread which used it.And then call malloc_trim to release the idle memory. JDBC Connection is the database object.

@brianwyka Perhaps you need call malloc_trim by c code

@brianwyka FYI https://android.googlesource.com/platform/external/jemalloc_new/+/6e6a93170475c05ebddbaf3f0df6add65ba19f01/TUNING.md set $MALLOC_CONF to "dirty_decay_ms:0,muzzy_decay_ms:0,background_thread:true" can recycle memory from jemalloc to OS fastly. In my linux OS, it works. dirty_decay_ms,muzzy_decay_ms value shoule be set as you application scene.

> Hello, I'm also encountering this issue. I run a query server backed by DuckDB, which reloads tables into memory periodically to provide clients with up-to-date data. I noticed that...