QSync MacOs CPU Load

[DeeByZ]

Hello,

Help please, my QSync Client on Mac always load my CPU to 100%, even when all files sync already.

Client version 5.0.3.0328
MacOs Monterey 12.4
2,3Ghz Core i7
32Gb

Why?

Reboot and Re-install dont help me(

[nibbles2bits]

People will be curious at which version of the QSync client this started happening and whether it started after a QTS firmware update.

Does it happen on a Mac that's never had QSync?
Files left over in ~/Library can cause unintended issues.
Maybe open a support ticket with QNAP.

[DeeByZ]

Answer from QNAP, as always - no help

Hi

Thank you for contacting QNAP.

From the logs, the NAS model is TS-569L and firmware version is 4.3.4_20201006

Please update the firmware version to 4.3.4.1976 build 20220303

https://www.qnap.com/en/how-to/knowledg ... e-firmware

https://download.qnap.com/Storage/TS-56 ... 4.1976.zip

TS-569L has reached end-of-life (EOL). EOL means End-of-life, and EOL means no longer being maintained

Every product has End-of-life, such as Apple MacOS, Windows etc.

https://endoflife.date/macos

https://support.microsoft.com/en-us/win ... 66d9a53962

You may try to install and use the previous version of Qsync client

https://download.qnap.com/Storage/Utili ... 2.1314.dmg

https://download.qnap.com/Storage/Utili ... 1.0802.dmg

https://download.qnap.com/Storage/Utili ... 0.1916.dmg

https://download.qnap.com/Storage/Utili ... 0.1026.dmg

Thank you.

[nibbles2bits]

Unfortunately there's five moving targets
- your NAS version,
- your QTS version,
- your Mac version
- your macOS version
- your QSync version

Regardless you're having a big problem, and you've tried a lot of things to fix it.
My 451+ is so old the Celeron barely supports HW decoding x264. So I know how it goes.
Can we make forward progress? That's tricky because Apple is extremely aggressive
at the OS level doing subtle things that encourage you to buy a new Mac with Apple Silicon.
Also I'm not a developer who launches gdb a few times before lunch.

Debugging your hung thread or stuck process isn't easy because release software generally
has debugging disabled, as does MacOS in a lot of ways.

All those variables, the version combinations that need testing, and the debugging state,
lead most geeks to advise you to roll back to a set of versions that worked rather than
to hope you can identify the bug, then get QNAP to release a patch. The timeline for a
patch isn't realistic, given your older version combination.

So I'm deeply sorry to ask, did you 100% completely uninstall Qsync on the Mac, by dragging
it to the trash, along with all the left over files it puts in

/Users/deebyz/Library/Application Support
/Users/deebys/Library/Cache

and any others I didn't guess in your Library, and then empty your Trash, and reboot your Mac,
and then install a previous version of the QSync client? You really have to give it the
old college try.

Other than that careful switch to an earlier client version, you should reach out to Apple Support.
They may have heard of this, and they're definitely investigating reports against their latest Monterey.

Get ready for your next easiest variable you can test, your macOS version.
Your goal would be to get a couple of external USB storage drives that you
would install macOS onto and boot from. One drive gets the current macOS
installed from scratch, the next drive gets macOS 12.3.x if you can find it,
or possibly macOS 11. Those are clean installs, no migrating. It's okay to tell it
your Apple ID, but don't let it restore anything.

You can beat this, and it will cost you time, unless someone drops bye
who has insight. I'm just advising the "usual" because I don't have any today.

Good luck!