https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #26 from Martin Fuhrer <mfuh...@alumni.ucalgary.ca> ---
Strange, heaptrack was running the kdevelop session for around eight hours (and
kdevelop was running smoothly for most of this time, using a stable amount of
memory when I checked a couple times during the first few hours). A few
additional details I forgot to mention yesterday:
* I unpacked the AppImage and ran kdevelop from the usr/bin/ directory within.
* The default Debian 7 gcc (v4.7.2) is too old to build heaptrack, so I used a
custom install of the gcc v4.8.5 compiler and runtime for the heaptrack session
(kdevelop exhibits the memory leak whether it uses the gcc v4.8.5 runtime or
the default v4.7.2 runtime).
* When the kdevelop process refused to quit (and continued eating up memory), I
sent SIGTERM to the kdevelop process (not the heaptrack process).
Here are all the commands I ran (from csh):
set DIR="/scratch/home/mfuhrer/sw/db7/src/kdevelop-5.2.1"
setenv LD_PRELOAD $DIR/exec_wrapper.so
setenv APPIMAGE_ORIGINAL_QML2_IMPORT_PATH ""
setenv APPIMAGE_ORIGINAL_LD_LIBRARY_PATH $LD_LIBRARY_PATH
setenv APPIMAGE_ORIGINAL_QT_PLUGIN_PATH $QT_PLUGIN_PATH
setenv APPIMAGE_ORIGINAL_XDG_DATA_DIRS $XDG_DATA_DIRS
setenv APPIMAGE_ORIGINAL_PATH $PATH
setenv APPIMAGE_ORIGINAL_PYTHONHOME ""
setenv QML2_IMPORT_PATH $DIR/usr/lib/qml
setenv LD_LIBRARY_PATH $DIR/usr/lib/:${LD_LIBRARY_PATH}
setenv QT_PLUGIN_PATH $DIR/usr/lib/qt5/plugins/
setenv XDG_DATA_DIRS $DIR/usr/share/:${XDG_DATA_DIRS}
setenv PATH $DIR/usr/bin:${PATH}
setenv KDE_FORK_SLAVES 1
setenv PYTHONHOME $DIR/usr/
setenv APPIMAGE_STARTUP_QML2_IMPORT_PATH $QML2_IMPORT_PATH
setenv APPIMAGE_STARTUP_LD_LIBRARY_PATH $LD_LIBRARY_PATH
setenv APPIMAGE_STARTUP_QT_PLUGIN_PATH $QT_PLUGIN_PATH
setenv APPIMAGE_STARTUP_XDG_DATA_DIRS $XDG_DATA_DIRS
setenv APPIMAGE_STARTUP_PATH $PATH
setenv APPIMAGE_STARTUP_PYTHONHOME $PYTHONHOME
setenv KDEV_DISABLE_PLUGINS KDevWelcomePage
setenv LD_LIBRARY_PATH
/vega/xp/ThirdParty/gcc/db7/xprel/lib64:${LD_LIBRARY_PATH}
cd $DIR/usr/bin
heaptrack kdevelop >& kdevelop_log.txt
The last line was executing for about eight hours (until I killed kdevelop).
Could the track file be truncated because I killed the kdevelop process? Is
there some way to monitor the track file during the heaptrack session?
Unfortunately I don't have KDE 5, so can't build the heaptrack GUI to verify
the track file.
--
You are receiving this mail because:
You are watching all bug changes.
