Cache size quickly grows to hundreds of MB or even gigabytes
Please answer the following questions for yourself before submitting an issue.
- [X] I am running the latest version
- [X] I checked the documentation and found no answer
- [X] I checked to make sure that this issue has not already been filed
AdGuard version
stable,4.3.194
Environment
- OS:oneui5.1,Android13
- Device:Galaxy note20 ultra
- Firmware:SM-N9860
Root access
- [X] Yes, I have it.
What filters do you have enabled?
AdGuard Base filter, AdGuard Mobile Ads filter, AdGuard Chinese filter, AdGuard Popups filter, AdGuard Mobile App Banners filter, AdGuard DNS filter
What Stealth Mode options do you have enabled?
Hide your search queries, Send Do-Not-Track signals, Strip URLs of tracking parameters, Self-destruction of third-party cookies, Disable WebRTC, Block Push API, Block Location API
Issue Details
Steps to reproduce: 1.open the system app setting 2.to the “storage” 3.see the cache
Expected Behavior
cache maybe few MB
Actual Behavior
It can result in hundreds of MB or even tens of GB of cache being taken up
Screenshots
Screenshot 1:
Additional Information
Since it has been cleaned up, screenshots will be added later.
Probably a relevant message in AdGuard Telegram chat: https://t.me/adguard/176184/191741
The user has HUGE log files, who knows why. We'll look into it.
@Extreme-Icer could you please check if in your case the log files size is the culprit?
UPD: Similar reports: https://t.me/adguard/176184/190992 https://t.me/adguard/176184/191080
In which directory are the log files located?
@Extreme-Icer
May depend on the device. Check /storage/emulated/0/Android/data/com.adguard.android/cache/log
The log file is quite large
@Extreme-Icer @MySoul182 Thank you for reporting! We are aware of this issue and have already made some adjustments in the latest release version (4.3.194). So please upgrade to the latest stable version, then clear the cache and let us know the result after 12-24 hours of active usage.
@Extreme-Icer reports with the stable version.
@MySoul182 what exact version are you using? Could you please share the log file?
@ameshkov The cache may be transferred from a previous version if @Extreme-Icer used the nightly or beta and then upgraded to the release, so we need more details.
@Extreme-Icer please specify have you upgraded from 4.2 to 4.3 directly?
使用稳定版本的报告。
您使用的确切版本是什么?你能分享一下日志文件吗?
Sorry, I've updated to the latest version 4.4.1 and can't provide the log file, now it seems that there is no such bug. I was using version 4.3.178 before
@MySoul182 AdGuard for Android 4.4 nightly 1, correct?
yes
no i update from 4.3nightly to stable
@Extreme-Icer That explains a lot. Please clear the cache and keep an eye on the size for a while, this issue should have already been fixed in 4.3 stable.
Reopen this issue and let me know if the cache size goes wild again.
@Versty,@ameshkov, проблема актуальна на вчерашнем релизе 4.3.199
Details
@Spok1 Добрый день! Подскажите, чистили ли вы кеш после обновления на версию 4.3.199?
@Versty, я не обновлялся,я удалил прошлую и затем установил новую. В любом случая я обратно вернулся на версию 3.6,а вам отправил на почту письмо с логами! Анализируйте!
Reopened due to some users still reporting this issue after a clean install of AdGuard for Android release version 4.3.199.
on previous version i had familiar issue,app weight was 650mb,updating to newest version X.199 didn't solve that but after cleaning cache cleaning date uninstalling and check with sdmaid that app is fully deleted,installed vX.199 with old settings app size is 250mb. Maybe clean install doesn't solve cuz some files are leftovers in some folders
@nightznero
Maybe clean install doesn't solve cuz some files are leftovers in some folders
No, uninstallation correctly removes everything, and besides, sdmaid without root rights works just like a regular package uninstaller. So the problem specifically occurs on older versions of Android, in particular Android 7, on which this happens most often.If it doesn’t matter to you, then you can roll back to the previous version 4.1.x, or 3.6.11, where this does not happen.