Your message dated Tue, 28 Jul 2020 16:02:28 +0200 with message-id <[email protected]> and subject line Re: libblockdev-swap2: Swap seems to freeze the system has caused the Debian Bug report #922328, regarding libblockdev-swap2: Swap seems to freeze the system to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 922328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922328 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libblockdev-swap2 Version: 2.20-6 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, Not sure if I choose the right package. * What led up to the situation? When loading a tif image with feh of 100MB or (which was the next image) 749MB the system (Intel Pentium G630 with 4GB DDR3) freezes. /etc/sysctl.conf # swappines vm.swappiness = 10 * What exactly did you do (or not do) that was effective (or ineffective)? I presume it has something to do with swapping. I experience the same when I have 15+ tabs open in Firefox (latest version) When after a long wait the system comes out of the freeze and is usable again the system remains slower than before the view attempt of the image. When touching a 100MB tif image in Thunar the system freezes. It does not recover anymore -> hit the reset button * What was the outcome of this action? Waiting a long time or even hitting the reset button * What outcome did you expect instead? No system freezes or slugginess Release swap when it is not needed anymore so the system stayes responsive even after heavy swapping Some ideas for a solution: Get a message with a choice that swap can not handle the amount of data Make swap abandon the operation Give the user some sort of control. Do not let him get in a freeze / sluggines situation without recovery in an acceptable time * Some thoughts Maybe I did something wrong. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libblockdev-swap2 depends on: ii libblockdev-utils2 2.20-6 ii libc6 2.28-6 ii libglib2.0-0 2.58.3-1 libblockdev-swap2 recommends no packages. libblockdev-swap2 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Thu, 14 Feb 2019 16:15:22 +0000 MMnbJEE wrote: > * What led up to the situation? > > When loading a tif image with feh of 100MB or (which was the next image) > 749MB > the system (Intel Pentium G630 with 4GB DDR3) freezes. There are packages like "earlyoom" that are supposed to provide a nicer user experience in out-of-memory situations. I don't think there is a general solution that does the Right Thing in every situation though. Ansgar
--- End Message ---
