![]() ![]() Or, it could be when Google flips the switch and reaches the home stretch of its effort to decouple the Chrome browser from ChromeOS. And it may just be a cleanup of the Lacros browser flags. However, the “lacros-primary” flag is still there.Ĭlearly, something is changing with ChromeOS 116 here. At least not with the settings I’ve used for nearly two years. So I can’t enable the Lacros browser manually on that device. I also noticed that on a Chromebook running the latest ChromeOS 116 Beta Channel, the “lacros-support” flag no longer exists. ![]() But that’s just part of my thought process. That suggests that once ChromeOS 116 arrives, you won’t have to set those two experimental flags to “Enabled” to have Lacros on your Chromebook. Previously, the words “Pre M116”, meaning ChromeOS 116, were not present. This may be due to a more compute/memory intensive check process and might be kicking off check threads faster than they can resolve slowly burning up memory and CPU - max CPU might limit it but if the limit is max memory the result is generally going to be a locked system.Note that lines 11 and 12 above are the only changes to this documentation. These probably aren't good candidates for sync anyway, but it is possible the owner application detects a change and "fixes" it and then the client detects the change and "fixes" it back and forth, but only the nextcloud client seems to go crazy. I realize this is a nearly uselessly vague description and bereft of useful debug info, but it seems to afflict "live" local directories like games or earth cache directories. As with similar reported issues, it seems to be an issue with a live directory and my guess is that it happens when the application owner of a synced directory does something to the files of that directory that the client doesn't understand and causes a runaway condition of some sort. My problem comes and goes with syncing a live google earth folder (cute way to keep it synced across devices, but doesn't work). Hashing them could be sufficient, even unsalted, as rainbow table precomputes are unlikely to be worth the CPU, but it an awful lot of extremely sensitive data is bundled into the logs/debug archives. It would be very helpful to have an automatic redaction tool for log posts - usernames, IP addresses, filenames, directory paths. 3.3.6 to 3.4.0) Are you using the Nextcloud Server Encryption module?Įncryption is Disabled Are you using an external user-backend? Linux Which version of the operating system you are running.ģ.6.2 Is this bug present after an update or on a fresh install? None - files aren't actually synced, it is a desktop client problem Operating system When clicking on the share dialog, share by e-mail should be an option. The folder might hold 315MB or so of data. I suspect the cache folder upsets the client's filter routine which leaks memory. Note that they fill the cache dir, which is unselected for sync and also explicitly ignored Navigate around, this causes tiles to load - I suspect this is part of the issue.Let the client finish syncing and stabilizes with minimal memory footprint (~0.8% of 32GB) (this is stable under most of my use, just not with Google Earth. ![]() The share dialog does not display the option to share by e-mail.If Nextcloud Desktop Client is running and Google earth is launched (the google earth directory is partially synced, see details) then although the desktop client does not show that the folder is actively being synced, memory usage runs away and the client crashes or the system pushes swap so hard it becomes unusable. This is a duplicate report of #4646 - as the client and server are different and those fields are a big part of the reports, I'm creating this one for your documentation pleasure. I agree to follow Nextcloud's Code of Conduct.See Server Maintenance and Release Schedule and Desktop Releases for supported versions. Nextcloud Server and Desktop Client are up to date.This issue is not already reported on Github (I've searched it).This is a bug, not a question or a configuration issue.⚠️ Before submitting, please verify the following: ⚠️ ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |