Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element logging fills up device storage #7777

Open
catfromplan9 opened this issue Dec 13, 2022 · 6 comments
Open

Element logging fills up device storage #7777

catfromplan9 opened this issue Dec 13, 2022 · 6 comments

Comments

@catfromplan9
Copy link

catfromplan9 commented Dec 13, 2022

When I installed element and used it, system storage space (logs?) grew by several gb and after a few hours took up the entire system storage. To free up the space, I have to reboot and then click on element where it'll lag on the splash screen and presumably clear logs, only actually opening when the storage space is freed.

@catfromplan9 catfromplan9 changed the title Elemebt logging fills up device storage Element logging fills up device storage Dec 13, 2022
@jmartinesp
Copy link
Member

This sounds quite concerning, and I can't find a way to reproduce it myself. Also, by our setup, the maximum disk space logs should take is 750MB if extended logs options is enabled, 140MB otherwise.

If this is always reproducible on your end, could I ask you to:

  1. Verify that the app size is growing in "Settings app > Applications > Element Android".
  2. Describe what your usage is, if you have something enabled in Labs. This could help us pinpoint the feature that is causing your issues.
  3. Send a rageshake so we can take a look at the logs and try to find anything suspicious by either selecting 'Bug report' in the extended menu (3 dots icon) in the main screen or firmly shaking your phone.

@catfromplan9
Copy link
Author

This sounds quite concerning, and I can't find a way to reproduce it myself. Also, by our setup, the maximum disk space logs should take is 750MB if extended logs options is enabled, 140MB otherwise.

If this is always reproducible on your end, could I ask you to:

1. Verify that the app size is growing in "Settings app > Applications > Element Android".

2. Describe what your usage is, if you have something enabled in Labs. This could help us pinpoint the feature that is causing your issues.

3. Send a rageshake so we can take a look at the logs and try to find anything suspicious by either selecting 'Bug report' in the extended menu (3 dots icon) in the main screen or firmly shaking your phone.

Might not be element? The app size does not increase but when I use element the system storage size increases

@catfromplan9
Copy link
Author

A friend had the same issue and it applied to system storage as well, he was using stock android on a pixel phone. Starting to think it could be a memory leak or something that's causing a shitload of error/warning logs to be generated by the OS which then gets stored in system space? Just an idea

@catfromplan9
Copy link
Author

And I did notice that out of all apps Element is the slowest. Very unresponsive on a Pixel 5a, can be borderline unusable at times and when i have Element and SchildiChat both open my phone lags so much that the keyboard will often freeze for seconds at a time and i have to kill one. Have to run it in Unlimited battery mode as well or its also slower.

@jmartinesp
Copy link
Member

Are you using the F-Droid version? If you are, the problem might be related to this issue: #5244.

You can set up UnifiedPush by downloading the ntfy app and changing the 'Notification method' in Settings > Notifications to 'ntfy'.

@catfromplan9
Copy link
Author

Are you using the F-Droid version? If you are, the problem might be related to this issue: #5244.

You can set up UnifiedPush by downloading the ntfy app and changing the 'Notification method' in Settings > Notifications to 'ntfy'.

I disabled notifications

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants