RSAF has more bugs #22
Comments
|
Hmm, I'm not able to reproduce this. Can you upload the latest |
|
no crash.log is created for me because it was already hanging up and hadn't reacted to anything and the processes hung up due to RSAF |
|
|
|
the crash.log could not be created because it was also true when starting and it cannot run in the background, whether with or without battery optimization, RSAF does not run in the background |
|
if you don't get any further with the information and it happens to several people and then maybe everyone complains then it's your own fault |
chenxiaolong
added a commit
that referenced
this issue
Jul 1, 2023
RSAF was previously initializing rcbridge in MainApplication.onCreate(). Since all ContentProviders are initialized before the Application, it's possible to start receiving ContentProvider requests before rcbdige is initialized. This seems to trigger a deadlock in rclone and causes Android to kill RSAF due to the main thread hanging. When hitting this issue, crash.log would not be written because the killing is done via SIGQUIT, not via a JVM exception. This commit fixes the issue by initializing rcbridge in RcloneProvider.onCreate(). Fixes: #22 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
chenxiaolong
added a commit
that referenced
this issue
Jul 1, 2023
RSAF was previously initializing rcbridge in MainApplication.onCreate(). Since all ContentProviders are initialized before the Application, it's possible to start receiving ContentProvider requests before rcbridge is initialized. This seems to trigger a deadlock in rclone and causes Android to kill RSAF due to the main thread hanging. When hitting this issue, crash.log would not be written because the killing is done via SIGQUIT, not via a JVM exception. This commit fixes the issue by initializing rcbridge in RcloneProvider.onCreate(). Fixes: #22 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
when you close the app and then go to the files app the files app suddenly says "content could not be loaded right now" and when i start the app again android says "RSAF not responding"
The text was updated successfully, but these errors were encountered: