T
TW
Today I noticed high CPU, 98% on my computer in Task Manager. It started as
my computer being very slow. Even bringing up the Task Manager takes a long,
long time. I tracked it down to a .docx document that I work with every
business day since at latest May 2006.
I have two documents that exhibit this problem that I started to document in
May 2006. Document A is about 1.5MB. This is the one that I noticed the
problem today. Document B is about 7.5 MB. I started Document B as a
workaround of the high CPU in May 2006 by cutting out the contents of
Document A to Document B whenever high CPU occurs with Document A. So that I
avoid the high CPU while working on Document A every business day.
After upgrading to Word 2007 around Sept. 2007, I haven’t had high CPU till
today. Consequently I haven’t had to cut out contents from A to B from time
to time. I even had no high CPU with Document B, 7.5MB.
I am utterly disappointed today when I noticed high CPU opening Document A
and confirmed it with Document B. I almost want to suspect that one of the 12
Windows Updates I got on Aug. 13, 08 put this bug from 2006 back into the
product.
For your information, I had the following observations:
- I use a Document Map in each document.
- Minimize the document window brings the CPU down.
- Turning off the Document Map does not bring the CPU down.
- Click on the “X†on the upper right corner (Close) and HOLD brings down
the CPU. Even when the “X†is on another document that does not cause high
CPU.
- I tried Save As to another .docx, .rtf and .htm without solving the
problem. The problem comes back whenever I make changes to the document and
save no matter how small the change is.
my computer being very slow. Even bringing up the Task Manager takes a long,
long time. I tracked it down to a .docx document that I work with every
business day since at latest May 2006.
I have two documents that exhibit this problem that I started to document in
May 2006. Document A is about 1.5MB. This is the one that I noticed the
problem today. Document B is about 7.5 MB. I started Document B as a
workaround of the high CPU in May 2006 by cutting out the contents of
Document A to Document B whenever high CPU occurs with Document A. So that I
avoid the high CPU while working on Document A every business day.
After upgrading to Word 2007 around Sept. 2007, I haven’t had high CPU till
today. Consequently I haven’t had to cut out contents from A to B from time
to time. I even had no high CPU with Document B, 7.5MB.
I am utterly disappointed today when I noticed high CPU opening Document A
and confirmed it with Document B. I almost want to suspect that one of the 12
Windows Updates I got on Aug. 13, 08 put this bug from 2006 back into the
product.
For your information, I had the following observations:
- I use a Document Map in each document.
- Minimize the document window brings the CPU down.
- Turning off the Document Map does not bring the CPU down.
- Click on the “X†on the upper right corner (Close) and HOLD brings down
the CPU. Even when the “X†is on another document that does not cause high
CPU.
- I tried Save As to another .docx, .rtf and .htm without solving the
problem. The problem comes back whenever I make changes to the document and
save no matter how small the change is.