OneDrive causes extended fileproviderd CPU activity, hurts battery life

Anonymous

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.

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

Anonymous

2023-11-02T04:40:36+00:00
🎉 Best solution for now！🎉

According to https://www.reddit.com/r/macsysadmin/comments/u4bhy5/fileproviderd_causing_finder_to_crash_constantly/，

You may also run

fileproviderctl check -v

to see which files the process struggles with.

OR

Try:

fileproviderctl repair -v

It worked on some of my files but run it at your own risk.

In my case, I used ”fileproviderctl check -v“, then I found the files that caused the fileproviderd to run crazily.
- 2 files are 0kb in size(I moved them to another folder before, but they are still there, sync error)
- 2 folders are empty but with extension (It seems OneDrive doesn't work well with this).
🎉 When I deleted these files, fileproviderd calmed down.

No need to Reset OneDrive according to earlier comments.
Was this answer helpful?

9 people found this answer helpful.

0 comments No comments
Anonymous

2023-11-30T13:18:29+00:00

I had a lot of empty files(!) and "fileproviderctl check -v" returned a cryptic list of paths of the form "<FPFS>/O{12}C/p{2}s/N{19}r.pptx", making it very difficult to hunt them all down.

But since they're all empty files, then they're probably not very useful, so I ran

find . -type f -empty -exec rm -v {} ;

in my One Drive directory, which finds _all_ empty files and deltes them. It's a big hammer, but it works like a charm. No more CPU hogging by fileproviderd!
Was this answer helpful?

7 people found this answer helpful.

0 comments No comments
Anonymous

2022-07-12T04:34:13+00:00

Any luck solving this? I reset OneDrive a few times now... Those three processes are killing my battery....

fileproviderd

OneDrive

OneDrive File Provider
Was this answer helpful?

7 people found this answer helpful.

0 comments No comments
Anonymous

2022-03-14T08:28:48+00:00

I confirm this is still an issue on Monterey 12.2.1 and OneDrive 22.033.0213.0002 (standalone).

I've disabled Spotlight for OneDrive files, and no more problem (reboot).

Thanx you @md3x10
Was this answer helpful?

7 people found this answer helpful.

0 comments No comments
Anonymous

2022-01-25T10:14:43+00:00

This is still an issue; on reboot my two OneDrive clients stay at 200% CPU each and fileproviderd takes what's left, resulting in CPU temps > 100C and - also very worrisome - many GB's of data written by the OneDrive clients. Within a few min they both wrote > 3GB of data whilst they both are in sync (no files changed since reboot). This is very detrimental to the SSD if this happens every time and makes no sense.

The client constantly switches between showing 'You're all set' and 'Processing changes'.

Pausing syncing keeps fileproviderd active, even force-quitting does not work as long as the OneDrive clients are running. The daemon is also constantly restarted which makes this a very annoying problem and OneDrive doesn't work in this case.
Was this answer helpful?

6 people found this answer helpful.

0 comments No comments