You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a memory leak in the latest version. Since we upgraded I've seen sudden spikes of memory usage and Ubuntu starts shutting down other programs to avoid everything grinding to a complete halt.
i don't know what other info I can give you. The last time this happened I noticed that flow was taking 16GB or my 32GB of RAM.
Flow version: 0.331.0
I should add that we were upgrading from 0.327.0 and I didn't notice this there.
We're on 0.333 and the situation has improved but the problem hasn't gone away completely. Ubuntu regularly has to kill the flow process because it's taking up too much memory.
@Dagur Some more improvements have landed in more recent versions (specifically I'm thinking of 7e54ca1). Can you try 0.337 to see if this still happens for you?
Another update here: I've confirmed that memory use diverges depending on the allocator used in various builds. jemalloc seems to release memory more effectively than glibc malloc. The latter is used in our OSS builds. Trying out #9520 to switch builds to jemalloc.
Activity
gkz commentedon Sep 17, 2026
we will release a new version soon that should address this issue
SamChou19815 commentedon Sep 21, 2026
should be fixed by bb3be35
Dagur commentedon Oct 14, 2026
We're on 0.333 and the situation has improved but the problem hasn't gone away completely. Ubuntu regularly has to kill the flow process because it's taking up too much memory.
Dagur commentedon Oct 27, 2026
@gkz any news on this?
gkz commentedon Oct 28, 2026
@panagosg7 was making improvements here (not me)
panagosg7 commentedon Oct 29, 2026
@Dagur Some more improvements have landed in more recent versions (specifically I'm thinking of 7e54ca1). Can you try 0.337 to see if this still happens for you?
panagosg7 commentedon Oct 29, 2026
Another update here: I've confirmed that memory use diverges depending on the allocator used in various builds. jemalloc seems to release memory more effectively than glibc malloc. The latter is used in our OSS builds. Trying out #9520 to switch builds to jemalloc.