Rob Gillan
Rob Gillan
Hi @nektro @Jarred-Sumner , just trying to see if there's any permutations that assist in solving this problem. We have tried most versions of the nodejs-mongodb-native module from 6.10.0 through...
We have continued our testing with this simple script, that basically connects to the db using the latest nodejs-mongodb-native module (v6.20.0), both with Bun 1.3.1 and Nodejs 24.10.0. ``` //...
In case anyone else is struggling with this, we think we know where this is originating from. If you are connected to more than a single, local db (i.e. replicaset,...
so we have yet to try mongo 7.0.0, but running against a global, 31 node sharded cluster the following client options keep the memory leak minimised (still present, but slow):...
@sagi-chronom I was just about to say, you missed that setting. It is the combination of maxIdleTimeMS and minPoolSize:0 that slows the leak
So the mongodb module leaks. Less under nodejs when compared to bun but still leaks. We have not tested the new v7 driver as yet ourselves. If you don't set...
So please don't assume that the mongo module itself is not leaking. We have already raised a ticket with them on this, and whilst the leak is worse when using...
Yes we do produce single file executables: `bun build "source.ts" --compile --minify --sourcemap --outfile "build/target"`
We do have other applications running elsewhere where bun is running the typescript directly (and has mongo connection), and it still has OOM issues which were radically changed when we...
This would be really helpful :)