Release: 2.0.4.29 (canary) 2019-09-17

[kenkendk]

@ts678

There are multiple report of the CPU issue from multiple people on multiple OSs. I hope someone with the right tools (perhaps a profiler?)

I have a suspicion that it is the usage reporter:

Issues to address to get out of beta

Not sure why this is happening again, but it smells like the usage reporter going bonkers. It could be related to the updated CoCoL library, which may have tinkered just a bit with how the timeout exceptions are thrown so they are no longer correctly detected. That sounds like the usage reporter. It waits a little after starting before running the report submission code.

[ts678]

Perhaps someone could try turning it off in Settings as a workaround?

[Reimi]

That solved the CPU issue! So it is really the usage reporter.

[Ferdis]

Great, turning off these reports really helps! Thanks

[kenkendk]

@Reimi @Ferdis @ts678
I have found and fixed the problem and will send out a new canary build, hopefully today.

[BlueBlock]

@kenkendk

Yes. Deleted remote volumes stick around in the database for a while to fix issues where the backend reports the files as existing even though they have been deleted. Before this update, those files would continue to stay in the database, but they will now be purged from the database.

I do not see a case where it should have the effect that you report, but maybe @BlueBlock has a better idea of how the fix works?

I see a case I need to fix in the removal of deleted records in Remotevolume, but I can’t think of what would cause the issue as described by the user.