I have a VSTO Word 2010, VS2010 document level customization project where it typically works fine.
The issue is that on a few slower machines, Word will occasionally either throw the error "The customization assembly could not be found or could not be loaded.", or just crash when opening a document randomly. If you try to re-open the document
after the crash or error, it opens fine, so there is nothing wrong with the document or the customization.
The scenario is this:
1. Have a local folder of documents based on the customization - 30-40 of them.
2. Open a file, look at it for review, then close it. (it does not matter what you do in the document)
3. Open the next file for review as soon as the previous one is closed.
4. Every 10-20 openings you will get either a word crash or the above error. All files in the folder do open if you go back to it after the error or crash.
One customer sent me a hdmp where it showed Word with a threading issue as the cause of the crash.
It seems like it's possible that Word is trying to accesses the customization .dll before it has been properly released by the last instance of word. I've tried leaving the documents open and opening 10-20 at a time with no problem. It appears
to be related to closing the only instance of word, and then reopening it with the next file.
Because there is nothing wrong with the customization, and some machines don't show this problem at all, I'm not sure how to address the issue. The crash and error are upsetting to my customers, even if harmless.
I would appreciate some advice on where to look for the cause of this issue and/or anything I could change in my customization to avoid the problem.
Thanks for any help.
Here is some of the crash information - which happens if the above mentioned error does not:
Problem signature:
Problem Event Name: APPCRASH
Application Name: WINWORD.EXE
Application Version: 15.0.4454.1000
Application Timestamp: 509a4ea6
Fault Module Name: wwlib.dll
Fault Module Version: 15.0.4454.1004
Fault Module Timestamp: 50bdaab1
Exception Code: c0000005
Exception Offset: 00000000001fb326
OS Version: 6.2.9200.2.0.0.256.4
Locale ID: 1033
Additional information about the problem:
LCID: 1033
skulcid: 1033
And from the event log:
Faulting application name: WINWORD.EXE, version: 15.0.4454.1000, time stamp: 0x509a4ea6
Faulting module name: wwlib.dll, version: 15.0.4454.1004, time stamp: 0x50bdaab1
Exception code: 0xc0000005
Fault offset: 0x00000000001fb326
Faulting process id: 0x83c
Faulting application start time: 0x01ce2cd0d691d5a7
Faulting application path: C:\Program Files\Microsoft Office 15\Root\Office15\WINWORD.EXE
Faulting module path: C:\Program Files\Microsoft Office 15\Root\Office15\wwlib.dll
Report Id: 14f5b9cb-98c4-11e2-be7a-000c29d0272a
Faulting package full name:
Faulting package-relative application ID: