Re: [solved, mostly] CSRSS.EXE uses alarming amount of VM when Emacs is running

[Eli Zaretskii]

> From: Jason Rumney <address@hidden>
> Date: Sat, 11 Mar 2006 12:22:15 +0000
> Cc: address@hidden
> 
> Eric Hanchrow <address@hidden> writes:
> 
> > Apparently, Emacs was starting a number of invisible cmd.exes, each of
> > which was allocating a ton of memory for its window ... despite the
> > window's being invisible ;-|
> 
> It starts one such window. The reason for this is so that "emacs -nw"
> can work with the same executable.
> 
> > If anyone wants to repro this, here are the exact steps.
> 
> I don't see what we can do. By telling the system that you want a
> 9999x9999 buffer for your command windows you are telling it to
> allocate almost 100Mb for every such window - maybe double that by the
> sounds of your report - but that is an issue with csrss.exe, not with
> Emacs.

Can Emacs specify a non-default window size when it is started as a
GUI application?  Then we could arrange at least for the GUI session
not to use such a large window (since it's actually unused/hidden in
that case).

I agree that in the -nw invocation, this is not a bug, since the user
actually asked for all windows to have these dimensions.

Btw, Eric, I hope you know that, by clicking Properties instead of
Defaults, you can modify the dimensions of any specific window without
affecting the others.