all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: handa@m17n.org, emacs-devel@gnu.org
Subject: Re: Memory leak due to bidi?
Date: Wed, 03 Aug 2011 09:47:40 -0400	[thread overview]
Message-ID: <E1QobnQ-0002BS-EU@fencepost.gnu.org> (raw)
In-Reply-To: <87y5zatz2f.fsf@wanadoo.es> (message from Óscar Fuentes on Wed, 03 Aug 2011 15:16:40 +0200)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Wed, 03 Aug 2011 15:16:40 +0200
> Cc: Kenichi Handa <handa@m17n.org>
> 
> Kenichi Handa <handa@m17n.org> writes:
> 
> > Could you check the versions before and after my changes for
> > char-table handling?
> >
> > 2011-07-07  Kenichi Handa  <handa@m17n.org>
> >
> > 	* character.h (unicode_category_t): New enum type.
> >
> > 	* chartab.c (uniprop_decoder_t, uniprop_encoder_t): New types.
> > 	(Qchar_code_property_table): New variable.
> > [...]
> 
> The tip revision of my Emacs is precisely the revision you mention. So
> far no abnormal memory consumption. bidi-display-reordering is
> nil. GNU/Linux x86_64 (Kubuntu 10.10). Daily usage of Gnus, org-mode,
> magit, several programming modes and an assortment of minor modes. The
> current instance is running since 6 days ago. Previously it ran since it
> was built (07-07) for about 3 weeks. So there was plenty of opportunity
> for showing the leak.

Thanks for the info.

FWIW, I'm running the version that shows "the leak" on others'
machines for the last 10 days without exiting Emacs, and last time I
looked it had a 195MB memory footprint.  So I suspect the leak is
triggered by some specific usage patterns.  Or maybe I'm missing
something important.



  reply	other threads:[~2011-08-03 13:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02  4:42 Memory leak due to bidi? Eli Zaretskii
2011-08-02 19:12 ` Stefan Monnier
2011-08-02 19:16   ` Lars Magne Ingebrigtsen
2011-08-02 19:24     ` Andreas Schwab
2011-08-02 19:45       ` Lars Magne Ingebrigtsen
2011-08-02 20:12     ` joakim
2011-08-02 20:15       ` Lars Magne Ingebrigtsen
2011-08-02 20:37         ` joakim
2011-08-02 19:42   ` Andreas Röhler
2011-08-02 20:49   ` James Cloos
2011-08-03  1:10     ` Stefan Monnier
2011-08-03 13:30       ` Eli Zaretskii
2011-08-04 19:22         ` Antoine Levitt
2011-08-05  6:10           ` Eli Zaretskii
2011-08-03  4:29     ` Kenichi Handa
2011-08-03 13:16       ` Óscar Fuentes
2011-08-03 13:47         ` Eli Zaretskii [this message]
2011-08-04 16:00           ` Antoine Levitt
2011-08-04 16:30             ` Eli Zaretskii
2011-08-04 17:04               ` Antoine Levitt
2011-08-04 17:48                 ` Eli Zaretskii
2011-08-05  3:43                 ` Stephen J. Turnbull
2011-08-04  0:48         ` Kenichi Handa
2011-08-03 13:26       ` Andy Moreton
2011-08-03 13:44         ` Eli Zaretskii
2011-08-03 14:18           ` Stefan Monnier
2011-08-03 15:49             ` Andy Moreton
2011-08-03 16:16               ` Eli Zaretskii
2011-08-03 16:11             ` Eli Zaretskii
2011-08-03 16:01           ` Andy Moreton
2011-08-03 16:38             ` Eli Zaretskii
2011-08-04 23:15               ` Andy Moreton
2011-08-04  3:28             ` Stephen J. Turnbull
2011-08-04  5:15               ` Stefan Monnier
2011-08-04  5:19                 ` Eli Zaretskii
2011-08-04  9:23                 ` Stephen J. Turnbull

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1QobnQ-0002BS-EU@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=ofv@wanadoo.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.