Parser left in "Unexpected Error" status when closing multiple files.

[daFreeMan]

Win10, Excel2016 (desktop), RD .4235

Starting with one Excel file (A) open with a large VBA project, one Excel file (B) open with a very small VBA project, and 2 other Excel files (C & D) open with no VBA project (beyond the default Option Explicit) and the VBE open and parsed.

I saved all files that needed to be saved. I then closed file (B). I waited until RD status was Resolving References then closed (C) and (D) in fairly quick succession.

At some point during the process, the status said Unexpected Error. This time, it managed to finish the final "on close" parse and get to the Ready state. Usually, it has remained in Unexpected Error and no amount of parsing with only file (A) open will get it to clean up. I have to exit Excel & relaunch to get a successful parse.

Log with errors: RubberduckLog.UnexpectedError.txt

If When this happens again, I'll post a new log if it remains in Unexpected Error, in case there's anything different in there.

[daFreeMan]

And... it obligingly left me in Unexpected Error status on my next try! This time I had 3 no-code workbooks open (C, D & E). I closed (b), waited until it was Resolving References, then closed the other 3 (C, D & E) in reasonably quick succession.

Just for fun, here's the CE after I closed the last of them (the 2 named projects both start with W, but have unique names, never fear...): Only the SatSurvey file is still actually open, Task Manager proves it:

And the log: RubberduckLog.txt

and the log after attempting a manual reparse, just in case anything is different: RubberduckLog.txt