unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Moreton <andrewjmoreton@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Memory leak due to bidi?
Date: Wed, 03 Aug 2011 17:01:32 +0100	[thread overview]
Message-ID: <vz17h6u8owz.fsf@gmail.com> (raw)
In-Reply-To: E1QobkU-0001iA-T4@fencepost.gnu.org

On Wed 03 Aug 2011, Eli Zaretskii wrote:
>
> You can specify a revision by its date, see "-r date:YYYY-MM-DD" in
> the bzr docs.
>
> The version you want is 105007.
>
> It is easier to find this version by this:
>
>  bzr log --line -l500 | fgrep Handa
>
Thanks for this Eli.

As rev 105207 seems ok, I doubt that 105007 is the cause of the memory
usage problems. 

I've tried bootstrapping from the head of trunk today and observe rapid
memory usage growth, so it seems the problem is not a transient issue
caused by not bootstrapping a clean build.

I'm running rev 105300 to write this, which seems to be OK. I'll
keep bisecting to narrow down where things start misbehaving.

>> I've given up on using VC annotate in emacs after 10 minutes of bzr
>> thrashing my machine with zero output.
>
> ??? "time bzr annotate src/character.h" shows this for me:
>
>   real    0m21.802s
>   user    0m20.430s
>   sys     0m0.650s
>
> That's not long enough to be annoying, let alone 10 minutes of
> thrashing.  What am I missing?

I've no idea - I get similar performance from the command line. trying
to use VC annotate on the file within emacs was taking forever - I
didn't find out how long as I was too impatient to wait for it.

    AndyM




  parent reply	other threads:[~2011-08-03 16:01 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
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 [this message]
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

  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=vz17h6u8owz.fsf@gmail.com \
    --to=andrewjmoreton@gmail.com \
    --cc=emacs-devel@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).