There is potential for a race condition in current implementation of ExportsManager. A resource being read might get deleted by the cleanup cycle. On linux / macos this would be fine but on Windows it might throw an error.

We had a memory lock in place to avoid this but it was removed later in the PR. We need to bring the memory lock back to prevent this problem from happening.