Description of the Issue

1 MINUTE+ unresponsive hangs anytime NPP has network docs open to locations that may have drive spinup delays. This appears to be due to NPP's checks whether the document(s) open still exist, have changed, etc. These checks appear to happen synchronously upon regaining focus which causes this application deadlock (hang) condition.

Steps to Reproduce the Issue

1. Open 50 network-based (UNC or mapped) documents
2. Leave NPP idle for 30 min
3. Return and activate the NPP window and wait up to a full minute while every network-based location is called apparently synchronously to check those document states during which time, NPP appears totally unresponsive (hung) and will become so if clicked upon. Only upon leaving it alone to finish it's synchronous calls does it spring back to life and regain full normal functionality and responsiveness. It will continue to remain responsive as long as not allowed to sit long enough that remote locations may change drive spindown states and require additional time to spin back up to confirm those document(s) states.

NOTE: To much further demonstrate this behavior, remotely remove access or availability of one or more of the open document's network location(s). This can then result in multiple minute application deadlock (hang) condition before all the network timeouts are exhausted for the unavailable network location(s).

Expected Behavior

Prompts for any required network-based documents only after the background check occurs.

NOTE: This is how it should behave is how other apps do - a background non-blocking refresh. No need to change the checks, prompts, or anything else - simply make these calls Asynchronous instead of Synchronous.

Actual Behavior

Up to 30+ second hangs as every document opened via network has to spin up remote drives etc. and hangs the app while doing so.

TIA for any help addressing this!