From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#60255: Memory Leak Date: Wed, 10 Jan 2024 02:47:00 -0800 Message-ID: References: <83r0wr900v.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3249"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Ryan Wilson , 60255-done@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jan 10 11:48:11 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rNW82-0000fD-HR for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 10 Jan 2024 11:48:10 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rNW7p-0002fx-TD; Wed, 10 Jan 2024 05:47:57 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rNW7m-0002d3-Oe for bug-gnu-emacs@gnu.org; Wed, 10 Jan 2024 05:47:54 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rNW7m-0003pM-Fx for bug-gnu-emacs@gnu.org; Wed, 10 Jan 2024 05:47:54 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rNW7t-0004jJ-Q9 for bug-gnu-emacs@gnu.org; Wed, 10 Jan 2024 05:48:01 -0500 Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Wed, 10 Jan 2024 10:48:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 60255 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Mail-Followup-To: 60255@debbugs.gnu.org, stefankangas@gmail.com, ryan.wilson@everlaw.com Original-Received: via spool by 60255-done@debbugs.gnu.org id=D60255.170488363618009 (code D ref 60255); Wed, 10 Jan 2024 10:48:01 +0000 Original-Received: (at 60255-done) by debbugs.gnu.org; 10 Jan 2024 10:47:16 +0000 Original-Received: from localhost ([127.0.0.1]:42033 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rNW7A-0004gO-0K for submit@debbugs.gnu.org; Wed, 10 Jan 2024 05:47:16 -0500 Original-Received: from mail-ed1-x536.google.com ([2a00:1450:4864:20::536]:54272) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rNW78-0004gB-4R for 60255-done@debbugs.gnu.org; Wed, 10 Jan 2024 05:47:14 -0500 Original-Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-55590da560dso4882130a12.0 for <60255-done@debbugs.gnu.org>; Wed, 10 Jan 2024 02:47:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704883621; x=1705488421; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=Bre7sBONJ355gguT5l/VLErAfqi9HXrRAZs9IbIajwY=; b=Zym7Azi7l0zkfEBqMFHWMkuj06/kKJX1a/jyzdCPouqOxW7+nVxacFFLwm8zcCEKC7 uigsQSGdQKb0ZVxj48nComLdoYoLvNRx+NDgNHXGbF1TNOUkCNYQ17YXX/OkXrsyoxlq y6W6mTTHf7sqqKyEWPmqR79ckLMlPmyunVO+q72cepvkeZ5Pg2/b8DNStwUro7tf/nZY 7AQZRxk2ar+ozlKRISW2x0N4mZeavZ94nulNSTnvMWOyPOk+1IP/JnY4tQLM+9dfalVi MROAtaViKwc3ihp+b+VtumQWjYpH5uNPcEdk7sjah5w78/ljaeSICUZl3oEGY3x0Ur4u lmBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704883621; x=1705488421; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Bre7sBONJ355gguT5l/VLErAfqi9HXrRAZs9IbIajwY=; b=qNLulJrtClHyEa5ETDee2M9S3qHm922T4TdkobKVV0rvEvahpEiX6VuJbHcykvrzbF 7MatCLha2EGt/vnjdDHZIGab1y2bB0RGjx/aSiCVyPh3tMFwdjcWdphucTJPGj8P7rCZ AZ33+rayBVQNJfwZvYvOQV2V4fHTsvzUEL4cYNns57xh8cKr9lEg6ql85N7QmKc0/n4F Bdvw41YlH+1OXS8/f4Vo1IpUPshyIpHAwcFo8LPkL+qVI1S5A8UQ9Cdzjl2TMCA5lplw 0Bl7ZrhiXsPeM7OhIS6s6z32agF6XDs84FflQcmMs76Ot2umF7r7bozGgWuk4Q9QGimq Uk8A== X-Gm-Message-State: AOJu0YweiBAQgxdjhm9hkmoIPu7alN8pzjNTmD7T9Rw0jWJBCAb5QmGq R0EpLz48hfi8hWhJBqLPjBjPvgrVZtdxSFugCOaBfUdogio= X-Google-Smtp-Source: AGHT+IEhuJLYr8hJJHV19Jke6pz+W1SClf/3iydJwC2JsFboM2Zx+0SBWjDKn4MYs07Jg1BB/4IVHdi+tjM+vGVUnXo= X-Received: by 2002:a50:8e18:0:b0:553:4ec4:6980 with SMTP id 24-20020a508e18000000b005534ec46980mr304937edw.80.1704883620934; Wed, 10 Jan 2024 02:47:00 -0800 (PST) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Wed, 10 Jan 2024 02:47:00 -0800 In-Reply-To: (Stefan Kangas's message of "Mon, 4 Sep 2023 12:53:52 -0700") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:277700 Archived-At: Stefan Kangas writes: > Eli Zaretskii writes: > >>> Date: Wed, 21 Dec 2022 18:48:02 -0800 >>> From: Ryan Wilson via "Bug reports for GNU Emacs, >>> the Swiss army knife of text editors" >>> >>> I am just using emacs normally, mostly for typescript development, so >>> that might be the offending mode. Emacs is currently using 1.7GB of >>> memory, the other day I killed it after I saw it was using 19.9GB. I ran >>> memory report and nothing was reported as using significant memory. >>> >>> Memory report output >> >> It could be that a large part of memory that is mapped into the Emacs >> process is actually free, and glibc keeps it because it cannot release >> it to the system for some reason. >> >> When you get a significantly larger memory footprint again, please >> invoke the function 'malloc-info', and post here everything it writes >> to stderr stream. The data this produces will show how much memory is >> actually in use. > > Ryan, it seems like we need more information here to make any progress. > > Are you still seeing this? If yes, did you have a chance to look into > this any further? More information was requested, but none was given within 4 months, so I'm closing this bug. If this is still an issue, please reply to this email (use "Reply to all" in your email client) and we can reopen the bug report.