GNU logs - #21623, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#21623: 25.0.50; Another font memory leak 
Resent-From: Dima Kogan <lists@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Mon, 05 Oct 2015 19:04:02 +0000
Resent-Message-ID: <handler.21623.B.144407181725436 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 21623 <at> debbugs.gnu.org
From: Dima Kogan <lists@HIDDEN>
Date: Mon, 05 Oct 2015 12:03:27 -0700
Message-ID: <874mi516kg.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

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.

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.503 (Entity 5.503)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Dima Kogan <lists@HIDDEN>
Subject: bug#21623: Acknowledgement (25.0.50; Another font memory leak )
Message-ID: <handler.21623.B.144407181725436.ack <at> debbugs.gnu.org>
References: <874mi516kg.fsf@HIDDEN>
X-Gnu-PR-Message: ack 21623
X-Gnu-PR-Package: emacs
Reply-To: 21623 <at> debbugs.gnu.org
Date: Mon, 05 Oct 2015 19:04:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 21623 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
21623: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D21623
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#21623: 25.0.50; Another font memory leak
Resent-From: Lars Ingebrigtsen <larsi@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 01 Aug 2019 19:04:02 +0000
Resent-Message-ID: <handler.21623.B21623.156468619422656 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Dima Kogan <lists@HIDDEN>
Cc: 21623 <at> debbugs.gnu.org
From: Lars Ingebrigtsen <larsi@HIDDEN>
References: <874mi516kg.fsf@HIDDEN>
Date: Thu, 01 Aug 2019 21:03:07 +0200
In-Reply-To: <874mi516kg.fsf@HIDDEN> (Dima Kogan's message of "Mon,
 05 Oct 2015 12:03:27 -0700")
Message-ID: <87zhksg13o.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Dima Kogan <lists@HIDDEN> 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

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#21623: 25.0.50; Another font memory leak
Resent-From: Dima Kogan <dima@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 01 Aug 2019 19:38:02 +0000
Resent-Message-ID: <handler.21623.B21623.156468825110283 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Lars Ingebrigtsen <larsi@HIDDEN>
Cc: 21623 <at> debbugs.gnu.org
References: <874mi516kg.fsf@HIDDEN> <87zhksg13o.fsf@HIDDEN>
User-agent: mu4e 1.0; emacs 27.0.50
From: Dima Kogan <dima@HIDDEN>
In-reply-to: <87zhksg13o.fsf@HIDDEN>
Date: Thu, 01 Aug 2019 12:37:20 -0700
Message-ID: <87d0ho4qz3.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Lars Ingebrigtsen <larsi@HIDDEN> writes:

> (I'm going through old bug reports that have unfortunately not gotten
> any responses.)

Thank you very much for doing that


> That bug was fixed, I think, so the workaround wasn't necessary any
> more?  Are you still seeing memory leaks in this area?

I'm not using the lucid terminal anymore, so I'm not seeing this, but
I'm certain it's still an issue. The fix to 18403 WAS the workaround
that leaks memory (without the workaround emacs was crashing).

The commit that fixes 18403 by introducing a memory leak:

  commit 80465f41d7fc67d40f0a233504e295b127ad2c6b
  Author: Dmitry Antipov <dmantipov@HIDDEN>
  Date:   Tue Sep 9 07:22:36 2014 +0400

      * xterm.c (x_term_init): Consolidate duplicated code.
      [USE_LUCID]: Revert 2014-04-02 change (Bug#18403).  Add comment.
      (x_delete_terminal): Do not close X connection fd (Bug#18403).
      Add eassert and mark dpyinfo as dead only if it was alive.

When I was looking at this I wrote some tools to aid in debugging. The
blog post that describes these tools talks about this memory leak:

  http://notes.secretsauce.net/notes/2015/10/05_memory-leak-debugging-tools.html

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#21623: 25.0.50; Another font memory leak
Resent-From: Lars Ingebrigtsen <larsi@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Thu, 01 Aug 2019 19:45:02 +0000
Resent-Message-ID: <handler.21623.B21623.156468867211058 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 21623
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Dima Kogan <dima@HIDDEN>
Cc: 21623 <at> debbugs.gnu.org
Received: via spool by 21623-submit <at> debbugs.gnu.org id=B21623.156468867211058
          (code B ref 21623); Thu, 01 Aug 2019 19:45:02 +0000
Received: (at 21623) by debbugs.gnu.org; 1 Aug 2019 19:44:32 +0000
Received: from localhost ([127.0.0.1]:55336 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1htH03-0002sI-UP
	for submit <at> debbugs.gnu.org; Thu, 01 Aug 2019 15:44:32 -0400
Received: from quimby.gnus.org ([80.91.231.51]:45126)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <larsi@HIDDEN>) id 1htH02-0002sA-9m
 for 21623 <at> debbugs.gnu.org; Thu, 01 Aug 2019 15:44:30 -0400
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 <larsi@HIDDEN>)
 id 1htGzz-0003LH-6L; Thu, 01 Aug 2019 21:44:29 +0200
From: Lars Ingebrigtsen <larsi@HIDDEN>
References: <874mi516kg.fsf@HIDDEN> <87zhksg13o.fsf@HIDDEN>
 <87d0ho4qz3.fsf@HIDDEN>
Date: Thu, 01 Aug 2019 21:44:26 +0200
In-Reply-To: <87d0ho4qz3.fsf@HIDDEN>
 (Dima Kogan's message of "Thu, 01 Aug 2019 12:37:20 -0700")
Message-ID: <874l30fz6t.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org",
 has NOT identified this incoming email as spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 @@CONTACT_ADDRESS@@ for details.
 Content preview:  Dima Kogan <dima@HIDDEN> writes: > I'm not using
 the lucid terminal anymore, so I'm not seeing this, but > I'm certain it's
 still an issue. The fix to 18403 WAS the workaround > that leaks memory
 (without the workaround emacs was cra [...] 
 Content analysis details:   (-2.9 points, 5.0 required)
 pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 0.0 TVD_RCVD_IP            Message was received from an IP address
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
 [score: 0.0000]
X-Spam-Score: 0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Dima Kogan <dima@HIDDEN> writes:

> I'm not using the lucid terminal anymore, so I'm not seeing this, but
> I'm certain it's still an issue. The fix to 18403 WAS the workaround
> that leaks memory (without the workaround emacs was crashing).

I tried grepping the sources for the proposed patch and it didn't look
like it had been applied.  But I must have done something wrong, because
I can find it now.  Sorry for the confusion.

> When I was looking at this I wrote some tools to aid in debugging. The
> blog post that describes these tools talks about this memory leak:
>
>   http://notes.secretsauce.net/notes/2015/10/05_memory-leak-debugging-tools.html

Hm, interesting...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.