Debugging a memory leak that doesn’t show on heap profiling
While I am not familiar with Haskell daemon itself, answering your question “how it’d be possible to more effectively pinpoint such a leak”, it might be possible to use valgrind –leak-check=yes haskelldaemon (better if you compile it with debug info), OR, if the leak happens in shared library, try LD_PRELOAD=”yourlibrary.so” valgrind your-executable.