Oct 24 2022 06:31 AM - edited Oct 24 2022 06:33 AM
I keep running into situations where doing a 'Replace All' unexpectedly causes Word to stop responding. It's not only large files, numerous results, or complex strings/formatting, often it's a small file and a query/replacement that is simple and straightforward - rarely does Word warn me that 'it might take awhile'. Haven't seen any pattern to tell what might work fine and what will trigger Word to immediately - and infinitely - lock up.
Resource wise it will start drawing a ton of power and good chunk of my CPU, but nowhere near maxing out my machine. Memory consumption spikes for a while, but eventually drops considerably, eventually back to normal - but the power draw and CPU stay elevated.
I had hoped there would be a way to interrupt it, but it doesn't appear to be a separate process, and didn't respond to sending a BREAK, mashing ESC, etc.
Is there any way to pause/abort the Replace All process, or is the only option to forcefully close Word entirely?
I'm also curious to know if there are some settings/combinations that are more demanding than others, and/or if there's any indicators to distinguish situations when Word is actually FUBAR, versus just needing a bit more time.
Thanks!
Oct 24 2022 06:47 AM - edited Oct 24 2022 07:20 AM
Example:
Word has been 'Not Responding' for the last 90 minutes;
Parameters:
Oct 24 2022 07:35 AM
Oct 24 2022 03:05 PM