From: Antoine Levitt <antoine.levitt@gmail.com>
To: 9221@debbugs.gnu.org
Subject: bug#9221: Memory leak
Date: Fri, 05 Aug 2011 00:33:46 +0200 [thread overview]
Message-ID: <87ty9wajsl.fsf@gmail.com> (raw)
In-Reply-To: <jwvtya0pn55.fsf@iro.umontreal.ca>
05/08/11 00:14, Andy Moreton
>> On Wed 03 Aug 2011, Andy Moreton wrote:
>> I've tried building revs 105207 and 105208, each bootstrapped after
>> 'make clean'.
>>
>> While I can't be entirely sure, revision 105207 seems to behave
>> itself even after using gnus for a while.
>>
>> Revision 105208 seems to show growing memory usage, but nothing like as
>> fast as I observed before a full rebuild. After running for a few hours
>> memory usage seems to have stabilised at approx 93MB, and I'm not
>> seeing the > 1GB runaway consumption from before.
>>
>> I'll keep trying with newer builds to see if I can find anything that
>> produces the excessive memory usage again.
>
> I've been trying to bisect this, but it seems to take a while using
> emacs before the excessive memory consumption appears, so the test cycle
> is a little slow.
You can use Eli's patch (on emacs-devel) to print
bidi_cache_total_alloc, that's faster.
>
> The problems seems to appear somewhere between r105368 (good) and
> r105375 (bad).
>
> I'll keep looking at this to make sure I can get consistent results.
>
> AndyM
Is word-wrap t? If yes, does the problem go away when turning it off?
next prev parent reply other threads:[~2011-08-04 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 2:23 bug#9221: Memory leak Stefan Monnier
2011-08-02 4:39 ` Eli Zaretskii
2011-08-02 11:17 ` Antoine Levitt
2011-08-02 11:37 ` Eli Zaretskii
2011-08-02 12:18 ` Antoine Levitt
2011-08-02 23:53 ` Andy Moreton
2011-08-03 3:03 ` Eli Zaretskii
2011-08-03 9:04 ` Andy Moreton
2011-08-03 14:06 ` Andy Moreton
2011-08-04 22:14 ` Andy Moreton
2011-08-04 22:33 ` Antoine Levitt [this message]
2011-08-05 11:16 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ty9wajsl.fsf@gmail.com \
--to=antoine.levitt@gmail.com \
--cc=9221@debbugs.gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).