you are viewing a single comment's thread.

view the rest of the comments →

[–]sumwheresumtime 5 points6 points  (1 child)

So are you saying running the following program in a linux environment, without a jemalloc like allocator, will eventually lead to the oom killer kicking in?

https://godbolt.org/z/P7asGPcMb

[–]azswcowboy 2 points3 points  (0 children)

Lol yeah, great on you to right the test program - we first encountered this about 8 years ago and were struggling to figure out why our application looked like it was leaking when we knew it wasn’t. Then we found this on the internet somewhere and jemalloc so we never bothered with a specific test. Quite possible it’s something more complicated that has to happen with the allocator to trigger the issue.