Since I do not know whats the source of the strings in the map actually is, I can’t tell for sure. But if they are smaller parts of some huge string, copying might help.
But to be really sure, we had to see much more code.
Similar problems can occur when you steadily eat from an input binary and then hold a reference to the very last sub-binary somewhere.
And since this is a really complex matter, I pulled in 3 links, which I found randomly:
- https://www.erlang-solutions.com/blog/erlang-19-0-garbage-collector.html
- https://hamidreza-s.github.io/erlang%20garbage%20collection%20memory%20layout%20soft%20realtime/2015/08/24/erlang-garbage-collection-details-and-why-it-matters.html
- http://erlang.org/pipermail/erlang-questions/2012-November/070779.html
I’ve read the GC 19.0 article by myself about a year ago and it helped me a lot to understand how garbage collection and the BEAM are working. But I’m not sure anymore if the binheap was explained well there. Therefore I put the other 2 links as well.
