From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.bugs Subject: bug#38345: 27.0.50; Permanent increase in memory consumption after opening images (or pdfs) Date: Mon, 03 Aug 2020 06:52:15 +0800 Message-ID: <87wo2gy82o.fsf@localhost> References: <87sgme1ww7.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> <83o8x0rl6d.fsf@gnu.org> <87lfs2mzo8.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> <87lfs19shb.fsf@mail.linkov.net> <87a78gn5k5.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> <83sgm8ox3g.fsf@gnu.org> <87zhgflxmc.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> <83lfrzq1s1.fsf@gnu.org> <87d0d7w3tt.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> <83zhgaloc5.fsf@gnu.org> <87zhg7jmjg.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> <83h82ej03y.fsf@gnu.org> <87fthkokrx.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> <83y2vc44j4.fsf@gnu.org> <87k0yggbju.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24419"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 38345@debbugs.gnu.org, juri@linkov.net To: Lars Ingebrigtsen , Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Aug 03 00:54:10 2020 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 1k2Mrp-0006E3-BV for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 03 Aug 2020 00:54:09 +0200 Original-Received: from localhost ([::1]:34612 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k2Mro-00023U-E3 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 02 Aug 2020 18:54:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37664) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k2Mri-00023B-9n for bug-gnu-emacs@gnu.org; Sun, 02 Aug 2020 18:54:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:60356) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1k2Mri-0000Mb-0f for bug-gnu-emacs@gnu.org; Sun, 02 Aug 2020 18:54:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1k2Mrh-000641-Uw for bug-gnu-emacs@gnu.org; Sun, 02 Aug 2020 18:54:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ihor Radchenko Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 02 Aug 2020 22:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38345 X-GNU-PR-Package: emacs Original-Received: via spool by 38345-submit@debbugs.gnu.org id=B38345.159640878723246 (code B ref 38345); Sun, 02 Aug 2020 22:54:01 +0000 Original-Received: (at 38345) by debbugs.gnu.org; 2 Aug 2020 22:53:07 +0000 Original-Received: from localhost ([127.0.0.1]:43669 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2Mqp-00062s-C0 for submit@debbugs.gnu.org; Sun, 02 Aug 2020 18:53:07 -0400 Original-Received: from mail-pj1-f53.google.com ([209.85.216.53]:40607) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k2Mqn-00062O-BX for 38345@debbugs.gnu.org; Sun, 02 Aug 2020 18:53:06 -0400 Original-Received: by mail-pj1-f53.google.com with SMTP id d4so483023pjx.5 for <38345@debbugs.gnu.org>; Sun, 02 Aug 2020 15:53:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=5ah4tpj8CC8CCllPTWuR3tJ0NhQ+GmMWCtXb0GyNsN8=; b=iwGd8tMjcdAcJZLY8aUc5xFuGq0GRhVfukTWgBGUs/V16Sy8Npx9v8k/bUSllWLCXb 3c1ccmS12IwMBU71UeBjRfGW0qPPWPv1GUIXB4yeDz+b1fdZ67MW1GSW0wDmg9t5uY2W bxW4LdhCXeb6PVNWixzgA6FY2lCZKUeGOkgt1KIq9MO7TJrM0iqYegvAwaxWZPniSqw+ iJRPVvvsqn4036wr5DF13hDkwQz7Vr2odi1Eejr7y2Zrm4B66bBMyoBHSjFDeEQodKfh BYDrCrbXfdofjizbFoUF54Rw4Ys4F3zwTrSmgDg2xmzGtj35Mf0OJHNj6gNHQ0+xq6pe IyRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=5ah4tpj8CC8CCllPTWuR3tJ0NhQ+GmMWCtXb0GyNsN8=; b=AqLS0BweqfaEsD8/6XfSnzNSO55uWEio0bTWFrE/UM4siQTc4kVUPPlExRHOWRcAkm FQQ/lGEwEH0HN5+JRls8ZHN9rsnK+cT2W3Hw1+37vTFaSTEgnd/L/Ykc5CRB5DSqZwqK NJBPk+SGeRlUWXn+wupRKqX3ueipuVDynXTa2BmLyXNTOH028lK+Nmq6qjJMQK6bKIHD wllNUbnQMHA5TQcMlTjcsIzkzUMjlycqAyGQghXELz1H6xOdABzzIAXL6V/b9dTK95Q3 Nw4L+B8fgTu1+1KZIpxfvTE9cO31K7liMQlfRqVIdK1cgqTsSGt/dIcFVaeNZWfCmqDB TE7w== X-Gm-Message-State: AOAM530NlmLR//mHJcBADEPUWhJcAU10wHE7oa2vwf5fJ3ufaPB9acYK TVv+Ssju6DEkuuNis4Ejh08= X-Google-Smtp-Source: ABdhPJxTKtk0P1Djb44PFAbC9VUO7dSPnxbhLp+03HAMS2DzrJ5xAuAOzpyZ/UcFQnMIq5ARwssQFw== X-Received: by 2002:a17:90a:8909:: with SMTP id u9mr6841050pjn.119.1596408779330; Sun, 02 Aug 2020 15:52:59 -0700 (PDT) Original-Received: from localhost ([104.168.14.206]) by smtp.gmail.com with ESMTPSA id k4sm13081587pjg.48.2020.08.02.15.52.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 02 Aug 2020 15:52:58 -0700 (PDT) In-Reply-To: <87k0yggbju.fsf@gnus.org> 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" Xref: news.gmane.io gmane.emacs.bugs:183897 Archived-At: > If that's the case, then this bug report can be closed? I think so. Lars Ingebrigtsen writes: > Eli Zaretskii writes: > >>> However, looking at the C code, I don't understand then why the >>> memory consumption is increasing. I can only see that too many images in >>> c->images array can cause extra memory consumption, which cannot cause >>> the observed memory leak. >> >> I guess that's because the freed memory is not at the end of the heap, >> and this cannot be returned to the OS. > > This was half a year ago, and skimming this bug report, it seems like > this was the tentative conclusion -- there's no memory leak, just the > allocator not returning the memory back to the OS. > > If that's the case, then this bug report can be closed? > > -- > (domestic pets only, the antidote for overdose, milk.) > bloggy blog: http://lars.ingebrigtsen.no -- Ihor Radchenko, PhD, Center for Advancing Materials Performance from the Nanoscale (CAMP-nano) State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg