unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <ambrevar@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 28329@debbugs.gnu.org
Subject: bug#28329: 25.2; Eshell: 40M+ output: Stack overflow in regexp matcher
Date: Sun, 05 Nov 2017 14:58:47 +0100	[thread overview]
Message-ID: <87mv40omi0.fsf@gmail.com> (raw)
In-Reply-To: <87o9p1e1q1.fsf@users.sourceforge.net>


Alright, I run into this again while emerging qtwebengine on Gentoo.
Now I think about it, this is the only and systematic cause of the issue
for me.
I suspect that emerging / compiling Chrome or affiliated projects would
also trigger the issue.

This time I managed to save the output, 60M+ big.

I tried to following

- emacs -Q
- M-x eshell
- cat portage.output.log

It took about 2 hours to complete!  While it takes half a second to
paste to the buffer.
Damn! Eshell's filters are slow! :/

That being said, no issue doing that.  So the output "saved after the
fact" does not seem to produce the issue.

-- 
Pierre Neidhardt

Finagle's Seventh Law:
	The perversity of the universe tends toward a maximum.





  reply	other threads:[~2017-11-05 13:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-02  9:34 bug#28329: 25.2; Eshell: 40M+ output: Stack overflow in regexp matcher Pierre Neidhardt
2017-09-02 12:30 ` npostavs
2017-09-02 13:27   ` Pierre Neidhardt
2017-09-03  2:19 ` npostavs
2017-09-24 12:55   ` Noam Postavsky
2017-10-21  1:20     ` Noam Postavsky
2017-11-05 13:58       ` Pierre Neidhardt [this message]
2017-11-05 14:44         ` Noam Postavsky
2017-11-05 14:54           ` Pierre Neidhardt
2019-06-30  4:58 ` Stefan Kangas
2019-06-30  5:59   ` Pierre Neidhardt
2019-06-30  7:07     ` Stefan Kangas
2019-06-30 13:45     ` Noam Postavsky
2019-06-30 14:48 ` Mattias Engdegård

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=87mv40omi0.fsf@gmail.com \
    --to=ambrevar@gmail.com \
    --cc=28329@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).