You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to open a big .avi file (~400MB) from Google Drive and the Mounter ate a lot of memory during this operation (~1700MB). I'd even was not able to view this video file. Here is the screenshot of the Task Manager:
The text was updated successfully, but these errors were encountered:
a file size of ~400MB sounds a bit excessive - actually the largest size I've been able to transfer in any reasonable amount of time was 250MB. Looks like my access provider sucks.
Nevertheless you've touched onto something here. Due to the requirement of determining the unencrypted content size of cloud files during read operations and the fact that some cloud gateways return non-seekable Streams, DokanCloudFS resorts to buffering the content of encrypted files. This is likely the reason for the substantial memory usage that you observed.
I will try to see if I can avoid the present buffering behavior in a future version of DokanCloudFS.
- Reduced memory consumption on large content download for Google Drive (see viciousviper/DokanCloudFS#29)
- Implemented additional unit tests
- Updated .NET Framework to version 4.6.2
- Updated various dependencies
Hi
I tried to open a big .avi file (~400MB) from Google Drive and the Mounter ate a lot of memory during this operation (~1700MB). I'd even was not able to view this video file. Here is the screenshot of the Task Manager:

The text was updated successfully, but these errors were encountered: