StevenWhitaker

@jpsamaroo Here's a MWE that shows the ever-growing memory utilization. It took me running `main` about 120 times to get the OOM manager to kill worker 2 (I have 32...

I just ran the exact same code as in #61 (which in turn is the same as the MWE above but with a call to `enable_disk_caching!(50, 2^10 * 20)`). This...

I ran the MWE (with and without enabling disk caching) on Windows (not WSL 2). - Without disk caching: I ran `main` about 200 times and never ran into any...

I just tested the new releases of DTables.jl/Dagger.jl/MemPool.jl using the [reproducer I mentioned above](https://github.com/JuliaParallel/DTables.jl/issues/60#issuecomment-1808665528). Without disk caching enabled: - WSL 2 still experiences the situation where the OOM manager kills...

@jpsamaroo I ran the following code to grab the info you requested. Let me know if you need any other info. ```julia julia> include("mwe.jl"); for i = 1:200 totalmem =...

I added `@everywhere GC.gc()` at the start of each iteration. It delayed the OOM issue until iteration 300, but the Julia process still was killed.

Any updates yet on this front?

@jpsamaroo I tried using the default value of `MemPool.MEM_RESERVED[]`, 2 GB, and 10 GB, and in all cases I got the same error (that looks different than what I reported...

Oh, I thought JuliaLang/Distributed.jl#4 was only relevant if running code with multiple threads, but I'm running `julia` with `-t1`. But I will try again tomorrow with that fix. With disk...

My reproducer still fails. With JuliaLang/Distributed.jl#4 and JuliaData/MemPool.jl#75 and the most recent nightly build of Julia: `MemPool.MEM_RESERVED[]`: Default ``` $ ~/programs/julia/julia-9fc1b653c4/bin/julia --project -t1 --heap-size-hint=3G _ _ _ _(_)_ | Documentation:...