let’s find out.
first, take a look at the memory mappings consuming the most memory (PID 8833 is an httpd.worker instance):
generate a core file:
convert the beginning of the range to decimal, get the length of the range:
dump that section of memory as a string:
inspect. in my case, it was an inefficient database query running in cron (via an HTTP endpoint) that was stacking up on prior queries, resulting in a slow (but substantial) memory leak.