OneDrive causes extended fileproviderd CPU activity, hurts battery life

Anonymous
2021-11-16T19:19:22+00:00

UPDATE possible solution: Try OneDrive's bundled reset script https://support.microsoft.com/en-us/office/reset-onedrive-34701e00-bf7b-42db-b960-84905399050c 

Wasn't sure where to post this since there's no OneDrive topic.

I’m using OneDrive insider preview 21.225.1031.0005 on macOS 12.0.1, M1 MacBook Pro. Even when I am not interacting with any files in the OneDrive folder, OneDrive regularly has several seconds of 200+% CPU usage. Immediately after, fileproviderd has long periods of 90% CPU use. This is lousy for battery life. I found at least one mention on Twitter of the same thing. The OneDrive CPU activity is likely not new, but I presume fileproviderd is new with the new OS.

I have 15,000 files synced with 12,000 set to “always keep on this device”. (My account has one very large folder that is excluded from syncing.) I watched a couple times and saw that OneDrive app activity triggered about 2 minutes of fileproviderd activity. Since the OneDrive app often has activity even when I’m not doing anything, this means fileproviderd runs *a lot*.

When this happens, Console shows hundreds of lines like these (in big groups of similar lines; these samples did not come next to each other): 

default 09:31:09.436927-0800 fileproviderd ✍️  FP snapshot mutation: update<s:16420 p:16357 n:"a{59}m.jpg" doc sz:9456 m:rwx%<0> ct:1569351878.0 mt:1569351879.0 v:sver:{blob142} cver:{blob139} nsattr:<cap:rwdpf-e- ul:uploaded deco:<com.microsoft.OneDrive.FileProviderBadges.Pinned.Shared> userInfo:<21 keys>>> diffs:structure why:item changed

info 09:31:09.443150-0800 fileproviderd ✍️  reconciliation update:     <fs:✅  docID(6521) content:watch sver:fileID(46661205)/b{38}m.jpg cver:46662408@2:sz:165242> <-> <fp:✅  16288 content:watch sver:{blob142} cver:{blob139}> doc sched:utility#1637083869.443043 rank:1637083696518411264

info 09:31:09.615397-0800 fileproviderd ┏333ca  �� trigger: <private>

info 09:31:10.044795-0800 fileproviderd item changed <FPItem 0x1209be840:16603 f:"b{82}m.jpg" p:16582 sz:131 KB cap:rwet bt:1569351583 mt:1569351584 mode:rwx-- uti:public.jpeg ul:uploaded dl:fault>, rules: []

They all seem to refer to nonsense file name strings like a{59}m.jpg and b{82}m.jpg. Those names do not exist in my OneDrive.

I would most like to know if this is a Microsoft problem or whether I should open an Apple bug report.

Microsoft 365 Insider | Install, activate, and update | MacOS

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

53 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-12-01T16:38:29+00:00

    Still getting the problem here in Dec 2023 - currently using the Sonoma 14.2 dev betas - though this problem has been long-running for a while

    I nearly moved fully to google drive, but had pushback from the family group & just renewed for 15 months.... If I lose trust in onedrive I may just have to accept paying for google as well.

    I frequently see high fileproviderd etc. Errors from 'fileproviderctl check -v' include types like:

    2023-12-01 16:28:26.760 fileproviderctl[10540:2717802] 💣 FPCK failed completing: Error Domain=FPCKDomain Code=65 "(null)"

    <FPFS>/O{15}l/P{6}s/F{6}k.FacebookBeta_8xx8rvfyw5nnt!App: ❌ Left : is_empty_dir_with_extension

    <FPFS>/O{15}l/P{6}s/i{11}s/D{7}s.old/I{6}1.jpg: ❌ Left : is_dataless_in_FS_Snapshot_but_not_on_disk|is_evictable_on_disk_but_not_in_FS_Snapshot
    <FPFS>/O{15}l/G{23}s/m{31}s.pdf: ❌ Left : has_busy_date
    <FPFS>/O{15}l/b{5}s/c{3}e/c{3}e/U{3}s/C{3}e/N{52}1.regtrans-ms: ❌ Left : is_filled_with_zeros

    A lot of these make no sense, though clearly relates to pictures, documents.

    My last attempt was to completely uninstall onedrive, cleanup everything, and resync from scratch. That was only a few weeks ago, but the issues have returned

    I presume the high CPU occurs when it runs a periodic consistency check? Or is it caused by the 'errors' and are these errors harmless, data corruption... who knows. I imagine they just affect local, but pushing corruption up to the cloud is a concern.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2023-06-07T16:34:16+00:00

    I've looked at your original post and can't decipher where this script is, could you post it again?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-06-07T14:08:23+00:00

    Did you try the reset script that's linked at the top of the original post? I'm the original poster. I do not think I have had the problem in a long time, maybe since running that script.

    Like some commenters, I would say it's reasonable to suspect Apple bugs as the ultimate cause. Hard to say though.

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more