Word XP eats up memory

R

revyakin

When I start WORD XP, it always ends up crashing after after 10-15
min, showing a "no memory" error. I looked at the Windows Task Manager
list of pProcesses and it turns out that after being started and left
idle, WORD gradually eats up RAM (by eye, 100 K per sec). When the
memory usage exceeds my RAM (at about 200,000K), it obviously crashes.
This does not happen with other applications like Explorer.
Re-installing Office XP did not help.

What's wrong here? I am writing a proposal which is due next week, and
this Win is killing me.

Any feedback will be appreciated.
My "real" email is [email protected]
 
T

TF

Is this just one document or all documents? If it is one document, then it
is probably corrupt. If it is all documents, then maybe the printer driver
is corrupt.



: When I start WORD XP, it always ends up crashing after after 10-15
: min, showing a "no memory" error. I looked at the Windows Task Manager
: list of pProcesses and it turns out that after being started and left
: idle, WORD gradually eats up RAM (by eye, 100 K per sec). When the
: memory usage exceeds my RAM (at about 200,000K), it obviously crashes.
: This does not happen with other applications like Explorer.
: Re-installing Office XP did not help.
:
: What's wrong here? I am writing a proposal which is due next week, and
: this Win is killing me.
:
: Any feedback will be appreciated.
: My "real" email is [email protected]
 
L

Laura

I'm noticing a similar problem. I have twice lost the same file. The
document is about 6MB and includes some graphics, but is mostly text, tables,
bullets, etc. This last time, when Word got to the state where it wouldn't
save and was complaining about memory and then subsequently about file system
permissions, I looked in the task manager and Word was consuming almost 1GB
(yes gigabyte) of memory. I had been following the mantra of "save often" and
hit control-S about every 3-4 changes in the document. When I examined the
hard drive, I discovered that Word never actually saved the file to disk. It
appears like it was doing an "in core" save - which might explain 1GB of
memory. It appears that the only way to truely save a file in Word is to exit
the application. To make matters worse, when I closed Word, it removed the
recover file. Fortunately, I *was* able to print the document before closing
and then manually type in all the changes again.

Now, I just reconstituted the file again, saved and quit Word. Then I tried
a test. I reopened the file and Word was instantly consuming 20MB. Then I
made a change and saved. Wallah. The size in memory jumped an increment that
is equivalent to the size of the file. And no saved copy on disk. Pretty
repeatable. Pretty poor quality control.
 
Top