Future Bug: Nextcloud client on ChromeOS freezing the system

noseshimself commented 1 year ago

⚠️ Before posting ⚠️

[X] This is a bug, not a question or an enhancement.
[X] I've searched for similar issues and didn't find a duplicate.
[X] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
[ ] I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

Install Nextcloud Android on a ChromeOS system running the Android subsystem in a VM ("ARCVM") (most are these days, ARC in containers is dead).
Use chrome://flags to activate Fusebox (chrome://flags/#arc-nearby-share-fuse-box) which will connect Android-exported file systems via fuse (this will become the default in later versions, right now it is a beta release and thus kept behind a Developer Flag). At this point two new file systems will show up in the Files application, one called "Nextcloud", the other one "fusebox Nextcloud".
Open the folder of the plugged in file system(s) "fusebox Nextcloud" For some unknown (assumption: The Nextcloud client is not fetching any data ahead of its being needed) reason the directories are not showing files (but do show subdirectories) and need explicit reloading to fetch the entire contents (this has always been like this; it's a quirk of the Nextcloud client).
The entire ChromeOS is freezing and needs a cold boot

4 is interesting -- the idea behind locking up Android in a VM is "this should never happen".

Expected behaviour

Reloading (and displaying) all file information in the subdirectory.

Actual behaviour

I do not have the slightest idea what is happening behind the scenes but the system stops responding and needs to be turned off.

Android version

11 (... 114) via ARCVM

Device brand and model

ChromeOS v114 (stable), v115 and v116 (pre-releases)

Stock or custom OS?

Stock

Nextcloud android app version

3.25.0

Nextcloud server version

25.x

Using a reverse proxy?

Yes

Android logs

Even though additional logs are collected enabling chrome://flags/#fuse-box-debug there is nothing left after a reboot; it looks like the Android subsystem is getting a full reset during reboot and I'm not going to put my production environment into developer mode.

Server error logs

This is not a server problem; even if the server was committing a boo-boo a client should not (be able to) crash an entire OS.

Additional information

This is a rather low-priority thing. Standard operation of the exported file system is not impacted; it's only the fusebox connection that is not working and it will take some more time before fusebox will really become the standard interface.

This might be a problem that needs to be discussed with the ChromeOS team responsible for fusebox ahead of its general release if it can't easily be reproduced.

A feedback report after crashing (multiple times) has been sent using the built-in report tool and should show up in the Chrome bug tracker sooner or later (after classification).

Dropbox, Termux and OneDrive do not show this kind of problem but they don't need an explicit reload of directories to show files either.

joshtrichards commented 1 year ago

A feedback report after crashing (multiple times) has been sent using the built-in report tool and should show up in the Chrome bug tracker sooner or later (after classification).

If you have a link to this report, please add it here. I poked around and wasn't able to find one.

noseshimself commented 1 year ago

The issue generated from the feedback report seems to be restricted (which hints at a security related problem) so it still did not show up. Interestingly the problem is not showing up since upgrading my system to ChromeOS v118 so we might be able to close this.

nextcloud / android