Bug#997663: marked as done (general: bullseye, system freezes completely when firefox freezes)
Your message dated Wed, 26 Nov 2025 18:06:46 +0100 (CET)
with message-id <[🔎] 20251126170646.582E2BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #997663,
regarding general: bullseye, system freezes completely when firefox freezes
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 owner@bugs.debian.org
immediately.)
--
997663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997663
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: general: bullseye, system freezes completely when firefox freezes
- From: Jacob Kochems <jacobkochems+bugtracking@gmail.com>
- Date: Sun, 24 Oct 2021 00:50:17 +0200
- Message-id: <163502941733.8951.8814201898765028781.reportbug@laptux>
Package: general
Severity: important
X-Debbugs-Cc: jacobkochems+bugtracking@gmail.com
Dear Maintainer,
* What led up to the situation?
When using Firefox (FF) with many open tabs it sometimes freezes and takes the
whole system with it. At this point all mouse and keyboard input is ignored. In
every case so far there was at least one tab with a YouTube video open. I
suspect using a lot of memory is the trigger here.
* What exactly did you do (or not do) that was effective (or ineffective)?
I tried to switch to a different tty via Ctrl+Alt+F<N>: no effect.
I tried the magic SysRq key sequence: REISUB: no effect.
I tried SysRq + f to call oom_kill: no effect.
Only a hard reset (power cycle) was effective so far.
* What was the outcome of this action?
The system freezes ignoring all user input.
If a video was playing at that time a short audio sequence of that video keeps
repeating in an infinite loop.
* What outcome did you expect instead?
I expect to be able to kill the offending applications.
I expect the system (be it gnome-shell, the kernel itself or other critical
components) to be able to handle failing user space programs without freezing
themselves. That is why I consider this *not* to be a bug of FF, although a bug
in FF seems to trigger it. No user space program should be able to tank the
system by hogging up resources.
Since I was unable to recover the system from this state I cannot provide any
error messages.
Is there a log file I can inspect after the fact?
If so, what should I look for?
Do I have to activate additional logging for this?
Some system information:
$ uname -v -r -m
5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64
CPU: Intel Core i7, 4 Cores
RAM: 8GB
Please let me know if you need additional system information.
I would appreciate any insight into how to diagnose this.
Thank you for your time.
Best regards,
Jacob
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---
Reply to: