Running HeapTrack on https://www.mudlet.org/download/Mudlet-3.9.0-linux-x64.AppImage.tar produces the following: heaptrack stats: allocations: 0 leaked allocations: 0 temporary allocations: 0 Heaptrack finished! Now run the following to investigate the data:
What happens if you run ./Mudlet-3.9.0-linux-x64.AppImage --appimage-extract and then run Heaptrack on the extracted contents?
it works when you extract the appimage I suspect that the following happens: - AppImage loader gets tracked by heaptrack - heaptrack unsets LD_PRELOAD to prevent child apps from being tracked - AppImage loader loads actual internal app and launches it so what this request boils down to is essentially the capability to track child applications with heaptrack. I'd really like to see this too eventually, but that will require quite some changes internally.