We had reports of customers who experience an early product termination when calling "ADViewer.Viewer.Document.SourcePath" and no document has been loaded prior to making the call.
The issue has now been resolved and development have indicated that getting an empty document path is not a defect, as no one should try to use the API to get information about the document before the document is loaded. This, however, should not lead to a crash.
The crash no longer occurs now and the call is returning a blank string, which is as expected.
Our recommendations to user is that one should not try to use the API to get information about a document before the document is loaded.
Please let us know should you have any additional questions about the issue.