From nobody Tue Oct 22 17:16:58 2024 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XXzPR1JqBz5Vdv5 for ; Tue, 22 Oct 2024 17:16:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XXzPQ3k8Mz4Wkw for ; Tue, 22 Oct 2024 17:16:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1729617418; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yl2gadKbfgg7Hes1kFKkmVXqo88LD5MLVYY1suH4TpQ=; b=v4KLZaU1vskJKhWIlwc/kLTBwPOLC3O6lOJQrRhoIw60HiJL4RyLhsIaclBSGT6g9rC8Fk jX5kFiDMRHbenxjiM10stNa6bT5Rx1aY05V3FepSgKbe4/JQSf9cFl8l9pqB3qzn259i71 kRd4XYpUB25sb2IwVK1f4t9ecUw83Qqu2hBHRP9kvh3rv37iJrEhsiJBjbL0JVPGEKZTvO 9dgH8/kBRRNh5+eSMixd+WIAMD/e6FANiKBam/7c99+AJYWJXvOB+uiz3J8Psa+xak+8Yo S82WVoIP1Na5uNGtHiR44Es30u5HZZJ4xPWUXAIMZJxt2Saiv58a8pazSG4uUA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1729617418; a=rsa-sha256; cv=none; b=ny05Av376c14F+AMmySOu79mpEUl5zAjUQY3bARS2Yi5LuTTMUFt6hGlxGGEKEq8Jed0ef GQQYTy6sp+TRHqei3MEXDYAzVGHHpPCETp6JDRVytd6VO6it7TLELglUokcXzPXPVhcLwL pQaymR1FkdlqCg332QOvPKKUdJCjA/N2Dy6REclW+s8q8UxaljmMW5SYdzpixps1QzyG8Y y/f5aNhE5F5xuazTdMkMLyxZ5HeSU2ZWXc7ea8hih6xtQfYP8mRI7U5H5CHUNhLFdh5fZY YTtIRzbdM9R6gA0FADRFcNvXfQGL2yOcr00NtnXK5aF0xcCM6Pe8ohJ03BgUtw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4XXzPQ34d4zMMY for ; Tue, 22 Oct 2024 17:16:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 49MHGwSU002609 for ; Tue, 22 Oct 2024 17:16:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 49MHGwDi002608 for bugs@FreeBSD.org; Tue, 22 Oct 2024 17:16:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 280846] Low memory freezes / OOM: a thread waited too long to allocate a page Date: Tue, 22 Oct 2024 17:16:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: henrichhartzer@tuta.io X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280846 --- Comment #50 from Henrich Hartzer --- Thank you! That is interesting. So the memory can be reclaimed if pushed out to swap, but I wonder if swap would fill up fairly quickly. Running with all of the patches I had some more OOM behavior. I had a fairly light Firefox (a dozen tabs, nothing very heavy), some other processes, and ran Gimp. I couldn't get very far with Gimp. pid 1614 (firefox), jid 0, uid 1003, was killed: a thread waited too long to allocate a page iwn0: RF switch: radio disabled wlan0: link state changed to DOWN pid 11298 (firefox), jid 0, uid 1002, was killed: a thread waited too long = to allocate a page pid 1532 (firefox), jid 0, uid 1002, was killed: failed to reclaim memory pid 68014 (gimp-2.10), jid 0, uid 0, was killed: failed to reclaim memory When the system starts to lock up, I kill the RF switch which usually helps= it become more responsive. You can see the "a thread waited too long to alloca= te a page" error again. With my main Firefox process dead I tried Gimp again. I could barely use it before it died again. pid 69150 (gimp-2.10), jid 0, uid 0, was killed: failed to reclaim memory pid 98331 (keepassxc), jid 0, uid 0, was killed: failed to reclaim memory pid 1729 (telegram-desktop), jid 0, uid 1002, was killed: failed to reclaim memory Is "failed to reclaim memory" from not being able to swap out the dirty pag= es? I'm surprised by how much memory Firefox and Gimp use. --=20 You are receiving this mail because: You are the assignee for the bug.=