Package: rsibreak
Version: 1:0.9.0-3
Severity: normal
After long times without reboot the virtual memory of RSIBreak increases
very much (over 2 GiB). It happened more times that
hibernation failed because of not having swap space. Stopping RSIBreak
will free a lot of swap and the computer
can hibernate. The resident memory was under 100 MB.
In my understanding virtual memory is not the actual quantity of memory
that a program can't run without, so it can be taken away when needed or
it may be already overcommited, but it did prevent hibernation.
Could anyone check this behaviour and tell if this was the actuall problem.
I tryed replicating this bug more consistently, but running KDE 4 is
hard to get a 100 hours without logout.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (650, 'unstable'), (600, 'testing'), (200, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rsibreak depends on:
ii kdebase-runtime 4:4.2.1-1 runtime components from the
offici
ii kdelibs5 4:4.2.1-1 core libraries for all KDE
4 appli
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libgcc1 1:4.3.3-5 GCC support library
ii libplasma3 4:4.2.1-1 library for the KDE 4
Plasma deskt
ii libqt4-dbus 4.4.3-2 Qt 4 D-Bus module
ii libqt4-network 4.4.3-2 Qt 4 network module
ii libqt4-svg 4.4.3-2 Qt 4 SVG module
ii libqt4-xml 4.4.3-2 Qt 4 XML module
ii libqtcore4 4.4.3-2 Qt 4 core module
ii libqtgui4 4.4.3-2 Qt 4 GUI module
ii libstdc++6 4.3.3-5 The GNU Standard C++ Library v3
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension
librar
ii libxrender1 1:0.9.4-2 X Rendering Extension
client libra
ii libxss1 1:1.1.3-1 X11 Screen Saver extension
library
rsibreak recommends no packages.
rsibreak suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
