From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#21623: 25.0.50; Another font memory leak Date: Thu, 01 Aug 2019 21:03:07 +0200 Message-ID: <87zhksg13o.fsf@mouse.gnus.org> References: <874mi516kg.fsf@secretsauce.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="4598"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 21623@debbugs.gnu.org To: Dima Kogan Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Aug 01 21:04:17 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 1htGN6-00011C-JY for geb-bug-gnu-emacs@m.gmane.org; Thu, 01 Aug 2019 21:04:16 +0200 Original-Received: from localhost ([::1]:58550 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1htGN4-0001Z7-Ub for geb-bug-gnu-emacs@m.gmane.org; Thu, 01 Aug 2019 15:04:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37178) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1htGMu-0001Z1-Th for bug-gnu-emacs@gnu.org; Thu, 01 Aug 2019 15:04:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1htGMt-0000JS-4r for bug-gnu-emacs@gnu.org; Thu, 01 Aug 2019 15:04:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:46429) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1htGMs-0000JB-EN for bug-gnu-emacs@gnu.org; Thu, 01 Aug 2019 15:04:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1htGMs-0005ub-8S for bug-gnu-emacs@gnu.org; Thu, 01 Aug 2019 15:04:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 01 Aug 2019 19:04:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21623 X-GNU-PR-Package: emacs Original-Received: via spool by 21623-submit@debbugs.gnu.org id=B21623.156468619422656 (code B ref 21623); Thu, 01 Aug 2019 19:04:02 +0000 Original-Received: (at 21623) by debbugs.gnu.org; 1 Aug 2019 19:03:14 +0000 Original-Received: from localhost ([127.0.0.1]:55250 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1htGM5-0005tM-Rg for submit@debbugs.gnu.org; Thu, 01 Aug 2019 15:03:14 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:44408) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1htGM4-0005tE-2G for 21623@debbugs.gnu.org; Thu, 01 Aug 2019 15:03:12 -0400 Original-Received: from 77.18.62.220.tmi.telenormobil.no ([77.18.62.220] helo=sandy) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1htGM0-00032F-9b; Thu, 01 Aug 2019 21:03:10 +0200 In-Reply-To: <874mi516kg.fsf@secretsauce.net> (Dima Kogan's message of "Mon, 05 Oct 2015 12:03:27 -0700") 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:164256 Archived-At: Dima Kogan writes: > I'm continuing to hunt for memory leaks. The next largest one is caused > by a workaround in > > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18403 > > In that report issues were observed when deallocating a font, and a > workaround was to leak the memory. This is not an insignificant leak > (3kB at a time), and a better solution is desired. (I'm going through old bug reports that have unfortunately not gotten any responses.) That bug was fixed, I think, so the workaround wasn't necessary any more? Are you still seeing memory leaks in this area? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no