From: Eli Zaretskii <eliz@gnu.org>
To: Reiner Steib <Reiner.Steib@gmx.de>, 3021@emacsbugs.donarmstrong.com
Subject: bug#3021: 23.0.92; MEM FULL on Windows after some VC operations
Date: Fri, 17 Apr 2009 00:35:16 +0300 [thread overview]
Message-ID: <83ws9kjn8r.fsf@gnu.org> (raw)
In-Reply-To: <87d4bcqtwo.fsf@marauder.physik.uni-ulm.de>
> From: Reiner Steib <reinersteib+gmane@imap.cc>
> Date: Thu, 16 Apr 2009 21:29:27 +0200
> Cc:
>
> with the latest precompiled pretest version for Windows
> (http://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-23.0.92-bin-i386.zip),
> I got "!MEM FULL!" after doing some VC / PCL-CVS commands (viewing the
> revision log, diffs, ...) on rather big files. The repository is on a
> network share, i.e. no pserver, ssh, ... involved.
>
> As requested by Eli, I attach the information reported by
> Sysinternals' VMMap, both for the Emacs 23 process with "MEM FULL" and
> an Emacs 22.3 process on the same box.
Thanks.
> The laptop has 3 GB of memory.
> [...]
> Process: emacs.exe
> PID: 7068
>
> Type Size Committed Total WS Private WS Shareable WS Shared WS Blocks
> Total 400.344 363.360 291.112 270.448 20.664 17.636
Unless I'm missing something, looks like something might be wrong with
how we discover available memory on Windows: how come a process with a
400MB memory footprint says MEM FULL on a 3GB machine?
FWIW, I had a couple of days ago a similar incident: a 380MB Emacs
process running on a 1.5GB machine claimed to have passed 75% of
available memory.
next prev parent reply other threads:[~2009-04-16 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 19:29 bug#3021: 23.0.92; MEM FULL on Windows after some VC operations Reiner Steib
2009-04-16 21:35 ` Eli Zaretskii [this message]
2009-04-20 20:07 ` Reiner Steib
2009-04-21 4:23 ` Jason Rumney
2009-07-05 10:31 ` Reiner Steib
2009-07-05 16:02 ` Jason Rumney
2009-07-11 11:57 ` Reiner Steib
2009-07-11 11:52 ` Reiner Steib
2009-07-15 18:49 ` Reiner Steib
2009-07-15 18:55 ` Processed (with 2 errors): " Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ws9kjn8r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3021@emacsbugs.donarmstrong.com \
--cc=Reiner.Steib@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.