From nobody Sat Aug 10 17:48:03 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 4Wh7Y02w2Gz5SgFm for ; Sat, 10 Aug 2024 17:48:04 +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 4Wh7Xz63xNz4jxf for ; Sat, 10 Aug 2024 17:48:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1723312083; a=rsa-sha256; cv=none; b=Vmo1Lmjfd+0X52hWJAYV4x4KNDDyzhzMbcWwIIcQH+f00AczbQm7aHLGdkPHLL0lME3EGH a3oxih2+C8HcXKmoY5GRkm4/1JmylAvfXPFsp+ufNfXkbrDdBR0j3RoxBIipQGm5/i3szn MHErRNxF/U5RmdqxaE3Lj7FO/c8z0FmFPwGxbONU9QBCka2c4HXNmch6ln6EG5gzNzdUrC rdxRTd4dDXQd7hcn5suJKb7dwDTZULtuYlxiSOscxOPfMjma6bPtTrxl+ggh/rbismPSrL GHlxMjz6aQrVCXm2qNNGJsEt3hLeREkgc+tX0KoWHHyIrsISiAAgYIVjJive+g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1723312083; 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=n6hy+yeG8OJYS1GOqb6MazxvFJpXd+kbcdMlLV64RmI=; b=RKr7D+AbJBQLTN7BEg7mFAX8gzP0aAaeofn1lUwWuz0p92U1DeDpqUFoaP6JeA6wiiLpx4 x2dQWgFFoI64+adDudLLAwDqTa7txTZdjUIjE7o68d+q8mU0sAQwP3NfqGvn5TcOxwm2u2 ksXkXeWmmPfjZxDx8HiVZ7UDdMpyeepaAlxQFMegLf2fucXt24V1bKWwCj2XH9Uz9BLAco +T3o6gN39NqxCjEeYZ+Ydbnk0hMjz6fDos0iMjq4VCoCrDRejlG5XlX2PNn/D9MA8FLXOs 0tqyl6KrZT008CshKyKtVdx5MXjh9EHnTWT/+glF8+SCFsdsk0LB8ZJw3pCE/g== 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 4Wh7Xz5ff4z18kr for ; Sat, 10 Aug 2024 17:48:03 +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 47AHm3FH091036 for ; Sat, 10 Aug 2024 17:48:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 47AHm3qN091035 for bugs@FreeBSD.org; Sat, 10 Aug 2024 17:48:03 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 280671] Memory leak on FreeBSD 13.3 and 14.1 Date: Sat, 10 Aug 2024 17:48:03 +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: sre@truespeed.com 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=3D280671 --- Comment #5 from sre@truespeed.com --- Hi Mark Thanks for looking into this issue! I'll try and provide all the detail I c= an. Today is the 3rd day the Server's been running so it was likely to run into that state, and it has! I've captured the requested stats in two scenarios: - At the point of "minimum" available memory (just prior to when I would ex= pect it to start thrashing) - After I've killed most of the running processes and jails (to see what's still hogging it) sysctl_vmstats_thrashing.txt and vmstat_thrashing.txt show the stats before= I intervene. stopped_sysctl_vmstats_thrashing.txt and stopped_vmstat_thrashing.txt show the stats after I've killed most of the running processes. I've attached two more charts showing the last 12 hours before intervention= for Total Memory and Memory Types. To answer your question about Memory loss, we "lost" 1.5GB of Total Memory = over a ~9 hour period before I intervened and rebooted the box. (93.6GB usually,= and slowly dropped to 92.1GB) The total memory didn't return to usual after I killed processes, only after a reboot, and looking at the charts it reduced further after I killed processes. This was the top memory profile after I killed everything. Mem: 1691M Active, 859M Inact, 64G Laundry, 4495M Wired, 22G Free ARC: 2470M Total, 1530M MFU, 720M MRU, 7936K Anon, 20M Header, 192M Other 2021M Compressed, 5712M Uncompressed, 2.83:1 Ratio Thanks again, if there's anything else I can provide please let me know. SRE --=20 You are receiving this mail because: You are the assignee for the bug.=