@Dingo :-
Aye, to echo t'other Mike it's perfectly safe to clear the cache. The only downside being that, in the short term, webpages will be a wee bit slower to load.......at least until those pages are cached again.
An easier way to control this is to add this snippet of code to the end of the 'LAUNCH' script. It's modified from one that Marv cooked up for Ungoogled Chromium, which has no control over its cache size, this being one of those Google APIs that's missing from that browser. I've modified this to work with Brave-Portable:-
Code: Select all
yad --undecorated --center --text=" Do you wish to clear the Brave cache? " \
--button="YES PLEASE - clear cache":2 \
--button="NO THANKS - don't clear cache":1 \
#
foo=$?
#
[[ $foo -eq 1 ]] && exit 0
#
if [[ $foo -eq 2 ]]; then
rm -rf $HERE/PROFILE/spot/Brave-Browser/Default/Cache/*
/usr/lib/gtkdialog/box_splash -placement top -bg "#07FE18" -fg black -timeout 5 -text " ~~~ CACHE CLEARED! ~~~" && exit 0
fi
Copy it; open the 'LAUNCH' script with Geany, and scroll down to the bottom. Leave a blank line, then paste the snippet in. Don't forget to 'save'!
This will display a wee GUI when you close the browser, giving you the choice to clear the cache, or not.
============================
Because Brave runs as spot, you'll need to add some fonts into /root/spot.......otherwise you'll have no text in the wee GUI, just a collection of little boxes. To fix that, install the wee .pet I've attached to this post; it'll install the DejaVuSans font to /root/spot/.local/share/fonts/default/TTF. I've tested this in my own Xenialpup64 just a few minutes ago; it works fine.
So; add the code snippet to 'LAUNCH', and install the .pet. That'll give you control over whether to clear the cache or not....
Let us know what happens, please.
Mike. 
