GNU bug report logs - #31585
27.0.50; 112GB Virtual Memory; 102MB working set

Previous Next

Full log

Message #22 received at 31585 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: markusffm <at> fn.de, 31585 <at> debbugs.gnu.org
Subject: Re: bug#31585: 27.0.50; 112GB Virtual Memory; 102MB working set
Date: Sun, 27 May 2018 19:11:24 +0300

> From: Noam Postavsky <npostavs <at> gmail.com>
> Date: Sun, 27 May 2018 09:17:52 -0400
> Cc: "markusffm <at> fn.de" <markusffm <at> fn.de>
> 
> From: "markusffm\@fn.de" <markusffm <at> fn.de>
> To: Noam Postavsky <npostavs <at> gmail.com>
> Subject: Re: bug#31585: 27.0.50; 112GB Virtual Memory; 102MB working set
> 
> >
> >I meant, how did you start Emacs, and what actions did you take in Emacs
> invoked by emacs
> >before observing the 112GB virtual memory usage?
> no action. after running emacs for let me say an hour the size of the 
> working set increases to 170mb
> invoking emacs with -Q doesn't change anything either.

A working set of 170MB is quite normal.  What I don't understand is
how come such a moderate working set can cause a 112GB VM usage.

Any chance you could run some memory analyzing program and see what
part(s) reserve all that huge memory?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.