How to Install and Uninstall heaptrack.x86_64 Package on Fedora 36
Last updated: November 25,2024
1. Install "heaptrack.x86_64" package
Here is a brief guide to show you how to install heaptrack.x86_64 on Fedora 36
$
sudo dnf update
Copied
$
sudo dnf install
heaptrack.x86_64
Copied
2. Uninstall "heaptrack.x86_64" package
Learn how to uninstall heaptrack.x86_64 on Fedora 36:
$
sudo dnf remove
heaptrack.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the heaptrack.x86_64 package on Fedora 36
Last metadata expiration check: 5:18:07 ago on Thu Sep 8 08:04:50 2022.
Available Packages
Name : heaptrack
Version : 1.2.0
Release : 6.fc35
Architecture : x86_64
Size : 554 k
Source : heaptrack-1.2.0-6.fc35.src.rpm
Repository : fedora
Summary : A heap memory profiler for Linux
URL : https://cgit.kde.org/heaptrack.git/
License : GPLv2+
Description : 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
Available Packages
Name : heaptrack
Version : 1.2.0
Release : 6.fc35
Architecture : x86_64
Size : 554 k
Source : heaptrack-1.2.0-6.fc35.src.rpm
Repository : fedora
Summary : A heap memory profiler for Linux
URL : https://cgit.kde.org/heaptrack.git/
License : GPLv2+
Description : 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