No Exceptions were produced. If the program crashed, it closed as you described, or resumes in a misbehaving condition.
Since the program would occasionally resume, although misbehaving, and other times close, I guess you could say it would hang and freeze depending on if it came back or not. Whatever the case is, it would not respond for several moments until it made up it's mind which fate was certain.
I don't quite understand why your not getting a straight up crash like myself and other users. The issue is pretty consistent throughout any project I've worked when I've tried to test. Makes no sense. You using one of those new fangled quantum computers?
A May patch is a disappointing length of time to have to use malfunctioning software. The problem is, sometimes the user will forget that the issue exists. Then, for no other apparent reason other then Trimble doesn't feel it necessary to provide a patch in a timely matter, the user is faced with losing work/production because of a malfunctioning product. Sorry for being so blunt, but I doubt the checks used to pay for the software don't take 10+ weeks to clear. Please reconsider issuing the patch, and any future patches for known and proven defects, in a more timely manner.
Alan - thank you again for your help and efforts with this issue.