Jump to content
Covecube Inc.
  • Announcements

    • Christopher (Drashna)

      Getting Help   11/07/17

      If you're experiencing problems with the software, the best way to get ahold of us is to head to https://stablebit.com/Contact, especially if this is a licensing issue.    Issues submitted there are checked first, and handled more aggressively. So, especially if the problem is urgent, please head over there first. 

sausages

Members
  • Content count

    10
  • Joined

  • Last visited

About sausages

  • Rank
    Member

Recent Profile Visitors

34 profile views
  1. Unsafe shutdown on Windows restart

    Unfortunately yes - it occurred after my most recent reboot while using 975.
  2. Unsafe shutdown on Windows restart

    I'm encountering this problem on Windows 7 so Fast Boot cannot be the cause
  3. Unsafe shutdown on Windows restart

    I've submitted the drive tracing and troubleshooter logs, but wanted to mention that this is still consistently happening. I'm thankful I do not have a bandwidth cap and have fast upload speeds, otherwise the software would be completely unusable. EDIT: Furthermore, another quirk I've noticed is that attaching the drive often results in extraordinarily high memory usage (as seen in the attached screenshot) that momentarily cripples the computer. Is such behaviour expected?
  4. Unsafe shutdown on Windows restart

    Hello, I'm having an issue where at least 50% of the time (if not more) when I restart my computer, CloudDrive seems to not shutdown properly and initiates a recovery upon startup. Looking at my Windows event log from the most recent occurrence, I found this: "The StableBit CloudDrive Shutdown Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service." I've attached a copy of the event file in case that helps. I'm running Windows 7 x64 and CloudDrive 1.0.2.964. Thanks! CloudDrive Shutdown Service.evtx
  5. Excessive memory usage

    I don't understand how you conclude this. As I've mentioned, previous builds of CloudDrive do not present this issue, and I'm fairly sure they utilize the same chunk system. To be clear, this isn't just a theoretical issue either. At least on my computer, the OS becomes entirely unusable once all memory is exhausted.
  6. Excessive memory usage

    Hm interesting. I've downgraded back to 730 for now, seeing under 200mb while uploading to ACD.
  7. Excessive memory usage

    Currently testing CloudDrive out, and was wondering whether this high level of memory usage is normal while uploading. I'm on build 739 if that helps. Thanks!
  8. Question about recovery if system fails

    Thanks for the response. That's the question though, what data is likely to be corrupted? Put it another way: if i'm uploading a batch of photos and my cache drive completely fails mid way, is it possible that photos I have already uploaded years ago sitting on the cloud server can be corrupted as well (i.e. the entire cloud drive and *all* cloud data is now lost)? I understand the rationale for having a cache and for the data being actively written to be lost in the event the cache drive fails, but data that has completely been uploaded should not be at risk - otherwise, what is the point of storing data in the cloud at all?
  9. Question about recovery if system fails

    Could you elaborate on this? If the hard disk I'm writing/uploading files from dies with data left over on the cache, the data already stored on the cloud may be corrupted? I'm just trying to gauge how secure data that's been written to the cloud is in the event of hardware failure.
  10. amazon api key not working

    I'm getting the exact same error, despite having the Security Profile along with the Web Settings pages set up correctly
×