Bug 394624

Summary: HeapTrack can't analyse an application inside an AppImage
Product: [Applications] Heaptrack Reporter: Vadim Peretokin <vperetokin>
Component: generalAssignee: Milian Wolff <mail>
Status: REPORTED ---    
Severity: normal CC: probono
Priority: NOR    
Version First Reported In: 1.1.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Vadim Peretokin 2018-05-23 16:01:46 UTC 
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:
Comment 1 probono 2018-12-27 21:48:52 UTC 
What happens if you run ./Mudlet-3.9.0-linux-x64.AppImage --appimage-extract and then run Heaptrack on the extracted contents?
Comment 2 Milian Wolff 2019-01-10 11:43:43 UTC 
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.