From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.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: Wed, 27 Nov 2019 00:24:40 +0800 Message-ID: <87imn6mwqf.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> 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> <83imn6skcc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="41680"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 38345@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 26 17:27:28 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iZdgV-000AjB-MN for geb-bug-gnu-emacs@m.gmane.org; Tue, 26 Nov 2019 17:27:27 +0100 Original-Received: from localhost ([::1]:56832 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZdgU-0004h0-D9 for geb-bug-gnu-emacs@m.gmane.org; Tue, 26 Nov 2019 11:27:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36684) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZdg8-0004ae-QO for bug-gnu-emacs@gnu.org; Tue, 26 Nov 2019 11:27:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZdg6-00058j-RH for bug-gnu-emacs@gnu.org; Tue, 26 Nov 2019 11:27:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46831) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iZdg6-00058V-HE for bug-gnu-emacs@gnu.org; Tue, 26 Nov 2019 11:27:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iZdg6-0004H7-EU for bug-gnu-emacs@gnu.org; Tue, 26 Nov 2019 11:27:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ihor Radchenko Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 26 Nov 2019 16:27:02 +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.157478559416394 (code B ref 38345); Tue, 26 Nov 2019 16:27:02 +0000 Original-Received: (at 38345) by debbugs.gnu.org; 26 Nov 2019 16:26:34 +0000 Original-Received: from localhost ([127.0.0.1]:52803 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iZdfe-0004GL-Du for submit@debbugs.gnu.org; Tue, 26 Nov 2019 11:26:34 -0500 Original-Received: from mail-pg1-f178.google.com ([209.85.215.178]:40097) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iZdfc-0004G8-T7 for 38345@debbugs.gnu.org; Tue, 26 Nov 2019 11:26:33 -0500 Original-Received: by mail-pg1-f178.google.com with SMTP id e17so9241837pgd.7 for <38345@debbugs.gnu.org>; Tue, 26 Nov 2019 08:26:32 -0800 (PST) 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=Aln3PUfrtWH6wQFU8DNvLIBJerQhTOxLigks/SPimIo=; b=EUxloJq5/6na6HJEmnYhm5NayJGhWjvuyY4LGtyzgZFCGanzd6Ni+CZdYmnDH/V0BU 1iBp9s5M2B+XJsD4S4q4B25AHDaElqwyYabm3wpEVOWeXB2qsHWpsoMdHgdJP+m7BxOP qMzeib+MWXKPm7FslYS3D8QKP1crxLUp9pebZvZCnO0bUHbmEQaSRuAeFWpoWMARZpUw V0xwzdrqSziHvacyPypoRiuREBNs+pfSt4iMOfkQPloKN6dHqL/HeDcvbtGaXRrNXc86 g4pn5ZGHKjn3ol8uSThUK2H3wW85evCHqG7MBufhkrXuQwT90BSaiB7Db+DdBfA5POIk +oIg== 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=Aln3PUfrtWH6wQFU8DNvLIBJerQhTOxLigks/SPimIo=; b=UqlegQqO5IfqSdAz7K4s29aDlxYcvpvDUbNvrr0tMzke76NPmmi0c7+f7IFnCNbVM+ 1J0MHg+Pt5PG4yDcjB0S7xE/au653W625TMjcqyz1oXNJWjmZgOCifVTfZfl83tEYAdW 22ispXv2INKJQuOmqIv/dSbafyKXVbGbeaaXVh9jnAOgWkhRdBa8eiDTSFlwvkhLv/zL SpTzL6/BQrDS6AWs8G97iQ+l3ubl9k3lQnOMZB6VUmfIRCf07jMjoN3+NQ5lxd5b28ef Pf7QYtpe669ut8yfn0t6TCIfkFk0RmZnl3vivnnnPE5wsveqxFoI1OKXypJy679sRkqe H6lg== X-Gm-Message-State: APjAAAUgrJLannhfywGSjCZFoB81+jilo69MCqN/RNNFlEm4t6v52DKH FI9oH4Q9T53x5HhvXwCiBkw= X-Google-Smtp-Source: APXvYqyhLkUAHoqZs1fCL9ZQ2Vc2nvVZkiHg5v5eZBoiq6wavCbtsvbT6Hasu83cNCnIfg+0bM3DMg== X-Received: by 2002:aa7:824d:: with SMTP id e13mr41894700pfn.35.1574785587058; Tue, 26 Nov 2019 08:26:27 -0800 (PST) Original-Received: from localhost ([104.250.131.79]) by smtp.gmail.com with ESMTPSA id g192sm13077954pgc.3.2019.11.26.08.26.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Nov 2019 08:26:25 -0800 (PST) In-Reply-To: <83imn6skcc.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:172446 Archived-At: > Does it help to call garbage-collect after killing each buffer and > before visiting the next image file? No. It makes no difference. > I don't understand the question, sorry. GC in Emacs is implemented in > C, not in Lisp. If you mean to use a garbage-collecting memory > allocator, then we once had that only for buffer text, but nowadays > system malloc is good enough for that, so we no longer use it. Doing > that for "normal" C code is not easy because it generally requires > double indirection for accessing data through pointers. Yes, I meant garbage collecting malloc. I don't know much about this topic. Just stumbled on an article saying that it can speed up performance. Regards, Ihor Eli Zaretskii writes: >> From: Ihor Radchenko >> Cc: 38345@debbugs.gnu.org >> Date: Tue, 26 Nov 2019 23:21:11 +0800 >> >> I did a small test by modifying my earlier lisp code to open and close >> the same image list sequentially: >> >> #+begin_src emacs-lisp >> (dolist (file (directory-files "~/Tosort/pictures&photos/" 'full ".*jpg")) >> (find-file file) >> (mapc #'kill-buffer (seq-filter (apply-partially #'string-match ".+.jpg$") (mapcar #'buffer-name (buffer-list))))) >> #+end_src >> >> The resulting memory usage graph is attached. >> >> What we can see is that the memory is indeed growing (as expected). >> Moreover, the memory consumption does not increase as much as if we open >> all the images together. However, the final heap size appears to be over >> 400Mb (from smaps), which is almost half of what was observed with all >> the images open at the same time. > > Does it help to call garbage-collect after killing each buffer and > before visiting the next image file? > >> P.S. Were there any attempts to implement garbage collection for emacs >> in C code? > > I don't understand the question, sorry. GC in Emacs is implemented in > C, not in Lisp. If you mean to use a garbage-collecting memory > allocator, then we once had that only for buffer text, but nowadays > system malloc is good enough for that, so we no longer use it. Doing > that for "normal" C code is not easy because it generally requires > double indirection for accessing data through pointers.