Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Huge memory consumption during opening big files in Google Drive #29

Open
psxvoid opened this issue May 27, 2017 · 1 comment
Open

Huge memory consumption during opening big files in Google Drive #29

psxvoid opened this issue May 27, 2017 · 1 comment

Comments

@psxvoid
Copy link

psxvoid commented May 27, 2017

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:
screenclip

@viciousviper
Copy link
Owner

Hi @psxvoid,

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.

viciousviper added a commit to viciousviper/CloudFS that referenced this issue Aug 31, 2017
- 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants