Re: Apps eating memory -> TS crashes

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thank's Josh, your explanation approved ;)

Now I still wonder how come the TS Server still crashes. CIM does not
indicate HW problems however, IMlog tells "Abnormal Program Termination
(BugCheck, STOP: 0x000000AB (0x00000001, 0x00001C38, 0x00000000,
0x00000050))". Only HEX address inside the inner parentheses vary. And this
happens on average of every second day...

Jan



"Josh Rosenberg [MSFT]" wrote:

Most apps act like you describe, on a TS or on a normal workstation. I'm
not seeing what is wrong here. TSes are just like any other computer
(albeit with improved resource sharing); if you run a few hundred programs
it will use up your memory.

Now causing the machine to actually crash is not an expected result, but
having it slowdown due to resource starvation is.

For the record, the behavior you describe is the way memory usage works
normally. The initially larger allocation is because the machine loads up
the executable's startup and normal operation code. When you minimize,
Windows tries to page out as much of the program memory as possible,
lowering the RAM used considerably. When you restore the window, it has to
pull the operating code (but not the startup code) back into system RAM, so
your memory usage will go back up, but usually not as high as it was
initially.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"Remy@work" <Remywork@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D0C26A0E-FF24-4A50-9BE7-6DEC7189279A@xxxxxxxxxxxxxxxx
Almost all applications installed in terminal server seems to act as
follows:
When starting the application for the 1st time, it takes f.ex. 80Mb from
TS
RAM. After you minimize the window, used memory drops dramatically,
typically
1/10 of original amount. After that, when you restore the window (from
minimized), it takes appr. 50 % of orig. amount and stays around there.
Normally application (in TS) is started only once so that it's window is
"normal size" or maximized. So if there are f.ex. over 100 users, it
easily
eats slowly the whole memory from TS until it finally crashes.
Do the applications (like MS Office) normally act like that when used on
Terminal Services? All Clients are win XPs, TS is 2003 EE w/SP1.

.

Relevant Pages

  • Crashes and the Blue Screen of Death!
    ... My Wife's computer spontaneously freezes or crashes. ... When crashes occur an error message window ... adding memory, changing memory modules, I decided to re-install windows. ...
    (microsoft.public.win2000.general)
  • Crashes and the Blue Screen of Death!
    ... My Wife's computer spontaneously freezes or crashes. ... When crashes occur an error message window ... adding memory, changing memory modules, I decided to re-install windows. ...
    (microsoft.public.win2000.general)
  • Crashes and the Blue Screen of Death?
    ... My Wife's computer spontaneously freezes or crashes. ... When crashes occur an error message window ... adding memory, changing memory modules, I decided to re-install windows. ...
    (microsoft.public.win2000.general)
  • Crashes and Blue Screen of Death
    ... My Wife's computer spontaneously freezes or crashes. ... When crashes occur an error message window ... adding memory, changing memory modules, I decided to re-install windows. ...
    (microsoft.public.win2000.general)
  • How do I debug PCI resource allocation problems
    ... problems on a new mainboard with Intel Q35 chipset and a shared memory ... <7>PCI: ... MEM window: disabled. ... VESA VGA frame buffer device ...
    (Linux-Kernel)