AdguardTeam
AdGuard filtering logs take up a lot of storage space
Oh, the storage usage is too high. I found that when continuously tapping "update" in the AdGuard app and rule updates fail, it consumes a lot of storage. Also, filter logs are reportedly taking up significant space. I hope to add hourly retention options for logs, such as one hour or five hours. Moreover, this data can't be cleared via cache cleanup. I'd like AdGuard's storage to be categorized to better manage and reduce excessive storage usage.
Hello @Lwb828 We already did some changes to the logging logic. Let's try to reproduce the issue in new version. First you need to:
- open Settings -> General -> App and filter updates
- choose Nightly in App update channel option
- go to Home Screen and tap on update button
- install 4.14 Nightly 4 (that's the version with new changes)
And please let me know the result.
I'm glad to see these optimizations. However, my previous message might not have been clear. What I meant is that when the AdGuard app updates, if rule updates fail, repeatedly tapping "Update" until AdGuard successfully updates all rules can cause the app to occupy a significant amount of storage space. This occupied storage cannot be freed by simply clearing the cache. Additionally, some users have reported that AdGuard's logs also consume substantial storage space, which similarly cannot be cleared through cache cleaning—it can only be removed by explicitly clearing the logs. Therefore, I request that AdGuard add time-based log retention options, such as one hour or five hours. Furthermore, the issue of excessive storage consumption caused by repeated rule updates and failed update attempts needs to be optimized. For these reasons, I kindly request and suggest that AdGuard implement categorized storage management to better manage its storage usage. I used AI for this translation, so please forgive any inaccuracies.
I'm using Adguard 4.12.1, and I'm experiencing the same issue: previously, the Adguard application data did not exceed 10-20MB, and now it totals 290MB. I have tried exporting the logs from the Adguard option, but the total does not exceed 10-20MB. Therefore, there is a bug in Adguard that is writing too much data, causing the Adguard application data to become too large, forcing me to delete it and reconfigure Adguard.
Hello @fdezsergio02 Can you tell me please how much usage time it could take to exceed the ~300MB mark of AdGuard's data?
Hello @fdezsergio02 Can you tell me please how much usage time it could take to exceed the ~300MB mark of AdGuard's data?
I flashed the phone on November 1st, and that's when I installed Adguard... it only has 14 days of logs, and I haven't used Adguard's built-in private browser. I can't see the contents of /data/data/com.adguard.android because that would require root access, so I don't know exactly what might be taking up that space.
UPDATE: I have seen a setting in the advanced options to extract Adguard databases, and it appears to be a .db file that is 190MB in size. The remaining 100MB still needs to be investigated, but a significant part could be there. I find it very strange that it weighs so much, since the application has only been installed for 14 days and usage is not very intensive (there are currently about 150.5K requests recorded in the statistics).
Another update: I deleted the app data on Saturday, it's now Monday (2 days later), and the app already has 184MB of data. Something is definitely wrong with Adguard. I thought it was an isolated incident and that deleting the data would be enough, but that's not the case.
Can you tell me please how much usage time it could take to exceed the ~300MB mark of AdGuard's data
In my opinion, under normal usage, AdGuard might take about a week at most to reach 300MB. However, as I mentioned, when AdGuard encounters errors during updates (rules, databases, etc.)—even after clearing data—storage usage can reach 400MB until all components show as up-to-date. Moreover, storage consumption gradually increases with each failed update attempt. I can't understand why this happens. It seems AdGuard is unable to delete residual data from failed updates, or this might be caused by an error in its update logic itself. AdGuard seems unable to delete residual data from failed updates, or...
Quoting myself from https://github.com/AdguardTeam/AdguardForAndroid/issues/5061#issuecomment-2750031834:
Can we have AG @ least compress, then encrypt old logs? I just found a total of over 3 GB of logs from only 3 days just using up space. .7z'ed, it's a much more acceptable 146 MB!
Can we have AG @ least compress, then encrypt old logs? I just found a total of over 3 GB of logs from only 3 days just using up space.
.7z'ed, it's a much more acceptable 146 MB!
This is a good approach, but in reality, many users do not require such extensive logging or log display. This method can partially alleviate logging pressure. Perhaps further processing of logs could be implemented, such as changing the log display period to a log recording period, with hourly log compression until automatic deletion after a specified duration. The log recording period could be set to intervals like 3 hours, 5 hours, 12 hours, or one day. Currently, logs are displayed as recorded, which may not involve deletion, and the minimum log display period is one day. Switching to a log recording period might inconvenience some users, so it would be preferable to add options like 3-hour recording. However, these measures do not address another critical issue: storage growth during updates if errors occur in rule updates, databases, etc. This problem also requires attention.
I have this problem on my Galaxy S25. AdGuard was using over 3GB. I did a fresh install and within a few days it was back up to 1GB (https://ibb.co/Z1phhnDT). I ended up going back to version 4.6.204 and I haven't had a problem since.
