Every time I attempt to "update citations & bibliography" it hangs.
I have run it in word safe mode. I have run the pc in safe mode. I have run it without backup, without autosave, without antivirus. I have disabled screensavers. I ran the office repair - no change. All to no avail.
It takes several hours to fall over, and the couple of times I watched the winword process memory usage, i saw it fall over at about the same memory use - about 1.8Gb. This computer still shows only 60% memory used so it's not like it's running out of RAM/swap space. It's behaving like an internal coding hard-limit on memory allocation was reached.
All the event viewer shows me is:
Faulting application winword.exe, version 12.0.6668.5000, stamp 5083137f, faulting module mso.dll, version 12.0.6662.5000, stamp 4fd67dd1, debug? 0, fault address 0x00b12066.
Is anyone else having this issue?
Is this fixed in Word 2010 or 2013?
Does anyone have any suggested workarounds?
Comments: ** Comment from web user: fredtheweasel **
OK - I was Wrong. It was not the Undo Stack that is bloating and eventually crashing.
When I ran your macro (thanks by the way - it worked perfectly on a test document) word exhibited all the same symptoms as using the application's own "update citations and bibliography" command. It ran for 3 hours and 40 minutes then crashed, with the winword process swelling from 39Mb at the start to about 1.1Gb at the time it crashed. Just like using word's internal command.
What I was able to do with your macro, was to add a statement to save the document at every update:
```
If ActiveDocument.Saved = False Then ActiveDocument.Save
```
I know this will be expensive in execution speed, but not as expensive as a month on this issue with no resolution and 2 years work down the drain. I have tested it on a truncated version of the document (it's slower than molasses) but at least I will be able to figure out how far it got, and maybe manually update the remainder, perhaps. Anyway, even with the many saves, the winword process still bloats in memory. I wonder if they are loading a copy of sources.xml into RAM for every citation?? Whatever Word is doing it is hogging memory and it doesn't scale.
Still no interest from Microsoft.
Thanks a bunch Yves, you have been very helpful. If I ever do get 'proof of life' in Microsoft I'll direct them to this site for other things they need to improve (like XSL handling). Talking of which, is it worth starting a "wish list" and/or a "bug list" for word citations, on this forum, that the community can add to?