From: Eli Zaretskii <eliz@gnu.org>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: 15156@debbugs.gnu.org
Subject: bug#15156: 24.3; !MEM FULL!
Date: Sat, 24 Aug 2013 17:27:21 +0300 [thread overview]
Message-ID: <83sixzgo52.fsf@gnu.org> (raw)
In-Reply-To: <86bo4njind.fsf@somewhere.org>
> From: "Sebastien Vauban" <sva-news@mygooglest.com>
> Date: Sat, 24 Aug 2013 15:57:42 +0200
> Cc: 15156@debbugs.gnu.org
>
> >>> Turn off flyspell and see whether it still happens?
> >>
> >> Quite complex,
>
> Eli wrote:
> > So you are saying that some (most?) of your sessions don't exhibit
> > this problem at all? Earlier, you said that the problematic sessions
> > are only several hours old, and this "once a week" seems to contradict
> > that, because if the memory footprint grows so much in just a few
> > hours, you should see these problems in almost every session. What am
> > I missing?
>
> I said that:
>
> - MEM FULL problem doesn't occur in Emacs sessions of tens of hours long, as I
> generally restart Emacs at least once a day.
No, you said:
> > And how long was that session up and running, before that happened?
> > (You can use the emacs-uptime command to answer the last question.)
>
> 15 hours, 14 minutes, 3 seconds
>
> But you must substract the night... So, in fact, something like 6 to 8 hours.
So, if you each day have a 15-hour long session, you should have this
problem almost every day. If you don't, that means when the problem
happens you do something relatively extraordinary. Maybe you could
try figuring out what that could be.
> In my head, it has never been clear that Emacs would be constantly growing, at
> all times (unconditionally), and that if I wait long enough, I won't escape
> the MEM FULL problem.
It shouldn't grow constantly. Here's what I see on my system:
Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
emacs 4388 8 6 140 195124 1:32:49.906 238:09:46.822
This session runs for more than 9 days.
> [1] Every 10s, I log "pslist emacs". I sometimes had two Emacs instances
> running in parallel.
The memory footprint grows almost monotonically, and too fast, IMO.
But it never goes anywhere near the 1.6GB mark, so I'm not sure we see
here something important. It would be interesting to see the memory
history of a session which does get to MEM FULL.
> I guess that "time gaps" such as:
>
> emacs 2440 8 6 236 67836 0:01:44.187 0:54:30.142
> emacs 2440 8 6 236 67836 0:01:44.234 1:14:33.897
>
> indicate that I closed the lid of my laptop, hibernating it for 20 minutes?
I don't think it's hibernation, unless pslist has some tricks up its
sleeve: when the machine hibernates, the elapsed time of all processes
stops advancing.
next prev parent reply other threads:[~2013-08-24 14:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 20:26 bug#15156: 24.3; !MEM FULL! Sebastien Vauban
2013-08-22 2:52 ` Eli Zaretskii
[not found] ` <mailman.538.1377139997.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.538.1377139997.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-08-22 7:16 ` Sebastien Vauban
2013-08-22 14:57 ` Eli Zaretskii
[not found] ` <mailman.570.1377183494.10748.bug-gnu-emacs@gnu.org>
2013-08-22 15:14 ` Sebastien Vauban
2013-08-22 16:00 ` Eli Zaretskii
2013-08-22 16:55 ` Dani Moncayo
2013-08-23 7:09 ` martin rudalics
[not found] ` <52170AC5.1070109-RbZlAiThDcE@public.gmane.org>
2013-08-23 22:22 ` Sebastien Vauban
2013-08-24 6:38 ` Eli Zaretskii
2013-08-24 8:55 ` martin rudalics
[not found] ` <52187509.4030904-RbZlAiThDcE@public.gmane.org>
2013-08-24 13:57 ` Sebastien Vauban
2013-08-24 14:27 ` Eli Zaretskii [this message]
[not found] ` <83sixzgo52.fsf-mXXj517/zsQ@public.gmane.org>
2013-08-25 7:39 ` Sebastien Vauban
[not found] ` <mailman.679.1377326354.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.679.1377326354.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-09-05 13:21 ` Sebastien Vauban
2013-09-05 14:22 ` Eli Zaretskii
[not found] ` <83sixjbb6x.fsf-mXXj517/zsQ@public.gmane.org>
2013-09-05 14:26 ` Sebastien Vauban
2013-09-05 14:48 ` Eli Zaretskii
[not found] ` <83ob87b9yy.fsf-mXXj517/zsQ@public.gmane.org>
2013-09-06 8:55 ` Sebastien Vauban
2013-09-06 9:20 ` Eli Zaretskii
[not found] ` <83ioyemhl4.fsf-mXXj517/zsQ@public.gmane.org>
2013-09-06 9:42 ` Sebastien Vauban
2013-09-06 9:58 ` Eli Zaretskii
[not found] ` <mailman.1455.1378461557.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.1455.1378461557.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-09-06 12:17 ` Sebastien Vauban
2013-09-06 13:15 ` Eli Zaretskii
[not found] ` <mailman.1471.1378473374.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.1471.1378473374.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-09-17 8:15 ` Sebastien Vauban
2013-09-17 8:23 ` Eli Zaretskii
[not found] <mailman.519.1377116896.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.519.1377116896.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-08-21 20:54 ` Sebastien Vauban
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=83sixzgo52.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15156@debbugs.gnu.org \
--cc=sva-news@mygooglest.com \
/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.