Parents (Total: 26)

The searched file hash is included in 26 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	4EB4F04D962F77EC21E2C5CE58E3F101
PackageArch	aarch64
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	umeabot <umeabot>
PackageName	heaptrack
PackageRelease	6.mga7
PackageVersion	1.1.0
SHA-1	14FBD5806A30007FFF765793D6A32F3FCFAD2E01
SHA-256	4723617D8A6376D374BE39581CBBCFF74B9EA58CF7E8141AF39F47E905614731

Key	Value
MD5	74667E5450648DCFBDD0DED4A4D5A728
PackageArch	x86_64
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	umeabot <umeabot>
PackageName	heaptrack
PackageRelease	6.mga7
PackageVersion	1.1.0
SHA-1	2231166AA09F2C61756BA0BACBE101587D95E446
SHA-256	8FF95271C2630443E0DAD3D59ED82CA760744E3166A3E917928D12F9C591BFF3

Key	Value
MD5	23CC2F04BB5B5E8670CDD3C7EAD86744
PackageArch	i586
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	wally <wally>
PackageName	heaptrack
PackageRelease	4.mga8
PackageVersion	1.2.0
SHA-1	25C0391D8BEAF3FC1E29A410403C04571F3D7D13
SHA-256	2CAB350F94434665EB1F3E4E298408236B963DA67D3737DE0165FDD2876F9F8F

Key	Value
MD5	AFEB65BC42484652712AB129C5B3D771
PackageArch	aarch64
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	Fedora Project
PackageName	heaptrack
PackageRelease	6.fc32
PackageVersion	1.1.0
SHA-1	34BC0AB51FA4AFE496BB316340C84B6E87819B5E
SHA-256	B7824EB09E74612ED418C9B4F0B23A1381287CA7C869A164F3A05ECBACB62EBE

Key	Value
MD5	D3176E9D61AC16871891BF8B7790814C
PackageArch	aarch64
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	wally <wally>
PackageName	heaptrack
PackageRelease	4.mga8
PackageVersion	1.2.0
SHA-1	3860FABAD5984D4F881453EA87766856303B41E2
SHA-256	524820343328A97055368C33BD351BE263EBA65023F4BEF09B5CCA7F9E2382C3

Key	Value
MD5	EA15CE972CAFC048DC767043C1A3BE9C
PackageArch	aarch64
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	Fedora Project
PackageName	heaptrack
PackageRelease	1.fc33
PackageVersion	1.2.0
SHA-1	4EF59378B34A1C5A5839EC21C0735D58B972C239
SHA-256	3494611CA4A73359743C223371156322EC102328E54795790FDF612D2D89061C

Key	Value
MD5	553B7B8F37175D247F68739B922ECF78
PackageArch	armv7hl
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	wally <wally>
PackageName	heaptrack
PackageRelease	3.mga9
PackageVersion	1.3.0
SHA-1	4F1CA0C0BF99D9683BAE6260431806333E2EAC47
SHA-256	861B66D5F10396545FC89BFFCC0B161514D29DACAC6D951A6D3B3A839F518D88

Key	Value
MD5	0199C8B243E6A9D67431EFBE78C0DC69
PackageArch	i586
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	papoteur <papoteur>
PackageName	heaptrack
PackageRelease	1.mga9
PackageVersion	1.4.0
SHA-1	5FEE6A7635637896A9F382861F47FEF21F277282
SHA-256	02697BD883F7809BD80785540EEA936D1346487B0E8F5FB560334419268EADCE

Key	Value
MD5	B90F70CB0782226E336C262F6CB7A855
PackageArch	armv7hl
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	wally <wally>
PackageName	heaptrack
PackageRelease	4.mga8
PackageVersion	1.2.0
SHA-1	63BE05B398D745C4DEB749424BB4C0F1CEE5FFA9
SHA-256	1965427126DEE79794D5DBBC7F156ED83BCC89472938D2665F12C287BF801508

Key	Value
MD5	DFBC24EC2DB29E9A172B8ACE6483B116
PackageArch	aarch64
PackageDescription	Heaptrack traces all memory allocations and annotates these events with stack traces.Dedicated analysis tools then allow you to interpret the heap memory profile to: - find hotspots that need to be optimized to reduce the memory footprint of your application - find memory leaks, i.e. locations that allocate memory which is never deallocated - find allocation hotspots, i.e. code locations that trigger a lot of memory allocation calls - find temporary allocations, which are allocations that are directly followed by their deallocation
PackageMaintainer	umeabot <umeabot>
PackageName	heaptrack
PackageRelease	2.mga9
PackageVersion	1.3.0
SHA-1	78B6B2AD520AD232D9E2718FDF197C855F52FD18
SHA-256	A74CDC246DB11FD5E7057571F9C768FAC592306A19264884FF45EC4B7938090E