https://www.boundaryml.com logo
Powered by
🟡 Potential Memory Leak in Version 0.219.0
# questions
c
Are there known possible memory leak issue in 0.219.0 (ArgumentValue trees retained)?
v
what client are you using?
c
Running BAML 
0.219.0
in a Node.js app, and it climbed to 2+ GB RSS over hours, then OOMKilled.
v
(nothing known that we know of)
interesting
i do know node has various memory leaks in general. i'll double check to see if we amplify that ourselves as well.
are you doing it with streaming?
c
For somemore context, I dumped bytes from /proc//mem at the leak pod. The address range is adjacent to where baml.linux-x64-gnu.node is loaded. The dumped bytes look the same as some of our baml function / template:
Copy code
"stats": Object {"age": Number(85), "size": String("LARGE"), "level": Number(7)}
v
(we saw some with go a while back but those were patched and specific to go)
c
I am using b.parse and b.request directly
v
got it, let me check sometime tmrw in that case and see if i can reproduce it
the modular api gets less battle testing then the main functions / streaming apis, so its possible!
thansk for flagging!
c
No problem, thanks for the quick reply!
5 Views
PreviousNext
Powered by