unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: memory consumption with pure-space-overflow (was: mem leak)
Date: Wed, 26 Apr 2006 15:44:40 +0200	[thread overview]
Message-ID: <v9mze8o3hz.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1FY5EL-0003qU-US@fencepost.gnu.org> (Richard Stallman's message of "Mon, 24 Apr 2006 13:52:13 -0400")

On Mon, Apr 24 2006, Richard Stallman wrote:

>     Is there any reason _not_ to make the build fail in this case?
>
> Yes.  Sometimes pure space overflow is due to a bug.  The best way to
> investigate it is to look inside the dumped Emacs.  If overflow made
> the build fail, you'd have to edit puresize.h before you could debug.

I noticed an enormous memory consumption of emacs, but I didn't notice
the warning during compilation for a long time and I have
`inhibit-splash-screen' set to t.

Shouldn't we add an appropriate `display-warning' in `startup.el' if
`pure-space-overflow' is t even if `inhibit-splash-screen' it t?
And/or add a "sleep ..." in the Makefile in this case.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  reply	other threads:[~2006-04-26 13:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24  7:33 mem leak LENNART BORGMAN
2006-04-24  8:01 ` Miles Bader
2006-04-24  8:18   ` Romain Francoise
2006-04-24  8:26     ` Miles Bader
2006-04-24  8:39       ` Miles Bader
2006-04-24 12:24         ` Stefan Monnier
2006-04-24 14:44           ` Miles Bader
2006-04-24 17:52         ` Richard Stallman
2006-04-26 13:44           ` Reiner Steib [this message]
2006-04-27  4:36             ` memory consumption with pure-space-overflow (was: mem leak) Richard Stallman
2006-04-27 13:52               ` memory consumption with pure-space-overflow Reiner Steib
2006-04-27 21:27                 ` Richard Stallman
2006-05-02 14:07                   ` Reiner Steib
2006-05-05 12:50                   ` Eli Zaretskii
2006-05-05 14:10                     ` Reiner Steib
2006-05-05 22:14                       ` Richard Stallman
2006-05-06 11:42                         ` Reiner Steib
2006-05-06 23:36                           ` Richard Stallman
2006-05-09 20:44                           ` Juri Linkov
2006-05-11  3:44                             ` Richard Stallman
2006-05-11 23:01                               ` Undocumented %-constructs (was: memory consumption with pure-space-overflow) Juri Linkov
2006-05-12  1:44                                 ` Undocumented %-constructs Johan Bockgård
2006-05-12 11:14                                   ` Juri Linkov
2006-05-14 23:29                                 ` Undocumented %-constructs (was: memory consumption with pure-space-overflow) Richard Stallman

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=v9mze8o3hz.fsf_-_@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).