If you request a certain file multiple times with the threaded option it will start loading the data again since it hasn't fully loaded since the first call. Future calls after the first one should see if it's being loaded instead of checking if its fully loaded. If it's being loaded then just return the first load call's promise
This is now fixed with the CacheRequester rewrite. If there is already a pending read it will return the pending read's Promise instead of starting a new read
If you request a certain file multiple times with the threaded option it will start loading the data again since it hasn't fully loaded since the first call. Future calls after the first one should see if it's being loaded instead of checking if its fully loaded. If it's being loaded then just return the first load call's promise