Jump to content

  • Log in with Twitter Log in with Windows Live Log In with Google      Sign In   
  • Create Account

Photo

Memory leak on attaching drive.


  • Please log in to reply
3 replies to this topic

#1 chcguy88

chcguy88

    Member

  • Members
  • PipPip
  • 18 posts

Posted 11 January 2017 - 01:52 AM

I am using version 1.0.0.802 Beta on Windows 7 64bit. I get a memory leak that immediately uses up all available memory on my system. This doesn't occur on Windows 8.1. It also seems linked to the size of the drive. I loaded up a 10 tb NTFS drive (encrypted) and cloud drive used 13 gigs of my memory (out of 32gb). I loaded up my 256tb NTFS drive (encrypted) and cloud drive uses 29 gb of my memory. Closing the drive immediatly brings my ram usage down to 2-3 gb. 

 

 

I saw this was fixed on newer versions of windows, but it seems like a current bug on windows 7 64 bit still. 

 

In addition to the memory leak - the cpu usage is 30% on a 6 core 12 thread cpu. As soon as stable bit is closed - it returns to a normal usage of 0-1% or less (with no other programs running).

 

 

Can anything be done to fix this?

 

Thanks!


  • Ginoliggime likes this

#2 Choruptian

Choruptian

    Member

  • Members
  • PipPip
  • 27 posts

Posted 11 January 2017 - 08:51 PM

I'm experiencing the same exact thing (1.0.0.800 & W7 64-bit)



#3 cnrd

cnrd

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 12 January 2017 - 02:52 AM

EDIT: Never mind, Windows was being wierd, made a new VM and it seems like it's working now.

 

Just as a heads-up: I'm also seeing problems with memory leaks on Windows 10 Pro (with all updates installed) and 1.0.0.802 beta installed.

 

Nothing else but CloudDrive running, and Windows is running on KVM, with files copied across a samba share attached inside Windows. (Using Windows to copy, not using the cloud drive as a samba share).

 

The VM have 4 cores and 6GB of RAM.

 

Snippet from log:

2:01:39.2: Warning: 0 : [ReadModifyWriteRecoveryImplementation:142] [W] Failed write (Chunk:1488, Offset:0x00000000 Length:0x01400500). The request was aborted: The request was canceled.
2:01:43.9: Warning: 0 : [WholeChunkIoImplementation:67] Error when performing master partial write. The paging file is too small for this operation to complete.

2:01:45.0: Warning: 0 : [TemporaryWritesImplementation:53] Error initiating temporary write (Chunk=1595, Offset=0x00000000, Length=0x01400500). Insufficient memory to continue the execution of the program.
2:01:45.0: Warning: 0 : [WholeChunkIoImplementation:180] Error on read when performing master partial write. The paging file is too small for this operation to complete.

2:01:45.1: Warning: 0 : [WholeChunkIoImplementation:61] Error on read when performing shared partial write. The paging file is too small for this operation to complete.

2:01:45.3: Warning: 0 : [TemporaryWritesImplementation:108] Error initiating temporary write (Chunk=1589, Offset=0x00000000, Length=0x01400500). Insufficient memory to continue the execution of the program.
2:01:45.4: Warning: 0 : [WholeChunkIoImplementation:180] Error when performing master partial write. The paging file is too small for this operation to complete.

2:01:45.4: Warning: 0 : [IoManager:67] Error performing I/O operation on provider. Retrying. The paging file is too small for this operation to complete.

2:01:45.6: Warning: 0 : [IoManager:61] Error performing I/O operation on provider. Retrying. The paging file is too small for this operation to complete.

2:01:47.1: Warning: 0 : [WholeChunkIoImplementation:53] Error on write when performing master partial write. Insufficient memory to continue the execution of the program.
2:01:47.2: Warning: 0 : [WholeChunkIoImplementation:53] Error when performing master partial write. Insufficient memory to continue the execution of the program.
2:01:47.2: Warning: 0 : [WholeChunkIoImplementation:159] Error on write when performing shared partial write. Insufficient memory to continue the execution of the program.
2:01:47.3: Warning: 0 : [WholeChunkIoImplementation:65] Error on read when performing shared partial write. The paging file is too small for this operation to complete.

2:01:47.6: Warning: 0 : [IoManager:65] Error performing I/O operation on provider. Retrying. The paging file is too small for this operation to complete.

2:01:47.7: Warning: 0 : [WholeChunkIoImplementation:108] Error on write when performing master partial write. Insufficient memory to continue the execution of the program.
2:01:47.8: Warning: 0 : [WholeChunkIoImplementation:108] Error when performing master partial write. Insufficient memory to continue the execution of the program.
2:01:47.9: Warning: 0 : [WholeChunkIoImplementation:185] Error on write when performing shared partial write. Insufficient memory to continue the execution of the program.
2:01:48.3: Warning: 0 : [IoManager:180] Error performing I/O operation on provider. Retrying. The paging file is too small for this operation to complete.

2:01:48.7: Warning: 0 : [IoManager:108] Error performing I/O operation on provider. Retrying. Insufficient memory to continue the execution of the program.
2:01:48.7: Warning: 0 : [IoManager:53] Error performing I/O operation on provider. Retrying. Insufficient memory to continue the execution of the program.
2:01:48.8: Warning: 0 : [WholeChunkIoImplementation:153] Error on write when performing shared partial write. Insufficient memory to continue the execution of the program.
2:01:48.9: Warning: 0 : [IoManager:159] Error performing I/O operation on provider. Retrying. Insufficient memory to continue the execution of the program.
2:01:50.1: Warning: 0 : [IoManager:185] Error performing I/O operation on provider. Retrying. Insufficient memory to continue the execution of the program.
2:01:50.1: Warning: 0 : [IoManager:153] Error performing I/O operation on provider. Retrying. Insufficient memory to continue the execution of the program.
2:02:07.7: Warning: 0 : [TemporaryWritesImplementation:142] Error performing read-modify-write, marking as failed (Chunk=1488, Offset=0x00000000, Length=0x01400500). The request was aborted: The request was canceled.
2:02:07.9: Warning: 0 : [WholeChunkIoImplementation:142] Error on write when performing master partial write. The request was aborted: The request was canceled.
2:02:07.9: Warning: 0 : [WholeChunkIoImplementation:142] Error when performing master partial write. The request was aborted: The request was canceled.
2:02:07.9: Warning: 0 : [WholeChunkIoImplementation:75] Error on write when performing shared partial write. The request was aborted: The request was canceled.
2:02:07.9: Warning: 0 : [IoManager:142] Error performing read-modify-write I/O operation on provider. Retrying. The request was aborted: The request was canceled.
2:02:08.0: Warning: 0 : [IoManager:75] Error performing read-modify-write I/O operation on provider. Retrying. The request was aborted: The request was canceled.


#4 Christopher (Drashna)

Christopher (Drashna)

    Customer and Technical Support

  • Administrators
  • 7,628 posts
  • LocationSan Diego, CA, USA

Posted 21 January 2017 - 09:36 PM

Could you do this: 

http://wiki.covecube.com/System_Freeze


Christopher Courtney

aka "Drashna"

Microsoft MVP for Windows Home Server 2009-2012

Lead Moderator for We Got Served

Moderator for Home Server Show

 

This is my server

 

Lots of "Other" data on your pool? Read about what it is here.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users