From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Fixxed buffer size for eshell
Date: Mon, 01 May 2017 17:26:14 +0300 [thread overview]
Message-ID: <834lx4k60p.fsf@gnu.org> (raw)
In-Reply-To: <20170501121545.mastnq7mxboyomyc@gmail.com> (message from Anast Gramm on Mon, 1 May 2017 15:15:45 +0300)
> Date: Mon, 1 May 2017 15:15:45 +0300
> From: Anast Gramm <anastasis.gramm2@gmail.com>
> Cc: help-gnu-emacs@gnu.org
>
> On Sun, Apr 30, 2017 at 10:21:03PM +0300, Eli Zaretskii wrote:
> > All I can say is that I cannot reproduce this here. I've ran this
> > command
> >
> > $ od prog
> >
> > where prog is a 13MB executable program. That filled the Eshell
> > buffer with 190,000 lines, and I still didn't see any slowdown. Not
> > sure why you do see Emacs getting slower (I tried C-b and C-p). Is
> > this similar to what you do in your case?
>
> Ok, I just run
>
> od /bin/mixxx in eshell.
>
> ( mixxx is 11.6 MB binary and od /bin/mixxx | wc -l gave me ~750000 lines )
>
> Emacs freezes when the buffer is at ~6500 lines,
> the whole daemon stoped so I had to restart it to write this email.
That's nowhere near what I see here. Some factor must be at work
here, but I have no idea what that could be.
> MPD started glitching the music that was on, and firefox crashed.
> Also my network manager restarted at that point.
>
> I managed to open a terminal and type pkill emacs, and everything went back
> to normal.
>
> Is it possible that memory depletion is causing this? I got 8gb...
Unlikely: my testing was on a 4GB machine.
But it's possible that your settings of virtual memory are
sub-optimal. Did Emacs start paging just before it froze? What does
the 'free' command displays on your system?
prev parent reply other threads:[~2017-05-01 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 10:02 Fixxed buffer size for eshell Anast Gramm
2017-04-30 14:21 ` Eli Zaretskii
2017-04-30 18:37 ` Anast Gramm
2017-04-30 19:21 ` Eli Zaretskii
2017-05-01 12:15 ` Anast Gramm
2017-05-01 14:26 ` Eli Zaretskii [this message]
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=834lx4k60p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).