B
brilliantatbreakfast
This is the damnedest thing:
I have a Word document that consists of a single table. When content
is added, the document can be up to 13 or more pages. It's reused
over and over again as a template for a newsletter that's embedded as
HTML into an e-mail.
The file consists largely of smallish .gif logos, some small clip art,
photos that average no more than 20K, text, and lines (done as Drawing
Objects).
Last week the person who maintains this file copy/pasted a 24MB image
into the file. This of course made the e-mail huge and caused Word
and her system to crash. We deleted this image from the file which
brought the file size down, but it's still hogging up to 99% of CPU
time WHILE IDLE!
And yet, if I open a second Word document, the CPU utilization goes
way down -- with two documents open!
Anyone have any idea what the problem could be? I have made sure that
all change tracking, background saving, and related utilization hogs
are turned off. Is it possible that this huge image corrupted the
file somehow? Except that if I use an earlier version of this same
file, the same behavior occurs.
I have a Word document that consists of a single table. When content
is added, the document can be up to 13 or more pages. It's reused
over and over again as a template for a newsletter that's embedded as
HTML into an e-mail.
The file consists largely of smallish .gif logos, some small clip art,
photos that average no more than 20K, text, and lines (done as Drawing
Objects).
Last week the person who maintains this file copy/pasted a 24MB image
into the file. This of course made the e-mail huge and caused Word
and her system to crash. We deleted this image from the file which
brought the file size down, but it's still hogging up to 99% of CPU
time WHILE IDLE!
And yet, if I open a second Word document, the CPU utilization goes
way down -- with two documents open!
Anyone have any idea what the problem could be? I have made sure that
all change tracking, background saving, and related utilization hogs
are turned off. Is it possible that this huge image corrupted the
file somehow? Except that if I use an earlier version of this same
file, the same behavior occurs.