OneDrive


Feedback by UserVoice

Jace Copier

My feedback

  1. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  OneDrive Sharing & Collaboration  ·  Flag idea as inappropriate…  ·  Admin →
    Jace Copier shared this idea  · 
  2. 2,823 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    369 comments  ·  OneDrive on Mac  ·  Flag idea as inappropriate…  ·  Admin →
    Jace Copier supported this idea  · 
  3. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  OneDrive on Mac  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jace Copier commented  · 

    We have over 1 million documents in a SharePoint online document library. As get get close to completing the synchronizing process, OneDrive begins to slow down immensely. The entire computer also struggles to do simple tasks (i.e. type in MS Word) until OneDrive eventually crashes.

    To re-launch OneDrive, it takes several minutes to sign back in, begin the synchronization process until eventually the application starts slowing down the entire computer again.

    This is definitely a huge concern. If a document library can hold 30 million items, the tool that is supposed to grant quick access to these files should be able to handle this as well.

    If this major issue could be addressed, it would substantially increase the adoption in my company, and i'm sure, many more companies as well.

    Jace Copier supported this idea  · 
  4. 612 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    45 comments  ·  OneDrive on Mac  ·  Flag idea as inappropriate…  ·  Admin →

    We have been working on several memory leak fixes recently. One of the main ones was fixed with Standalone version 19.086.0502.0008 and Store version 19.103.0527.0003. If you are not on one of those builds or higher, please update first. If you are still experiencing issues after updating, let us know. We will continue to focus on performance improvements, including memory utilization.

    Jace Copier supported this idea  · 

Feedback and Knowledge Base