هذه الصفحة غير متوفرة بلغتك بعد. أنت تقرأ النص الإنجليزي.
Knowledge base
Disk space and clearing the cache
Where the card is
Open the Engine screen: the "Storage on disk" card sits under the browser kernels card. The space is counted again each time you come to the screen, and the window does not freeze while it counts.
At the top are the totals: sessions and site data of profiles, their cache, browser kernels, extensions, flow screenshots, app logs, other and free space on the disk. Below is a table of all profiles by size with the engine and the last run.
What clearing removes
"Clear cache" removes the page cache, the code cache, the graphics caches and the cache of packages the engine downloaded. Cookies, logins, bookmarks, history, site storage and Service Worker stay, so the profile opens with the same logins.
After clearing, sites download their images and scripts again, and the first page load takes a little longer. To a site this looks like a normal browser after its cache was cleared.
- 1
All closed profiles
"Clear cache of closed profiles" under the totals; the window says beforehand how much will be freed.
- 2
One profile
"Clear cache" in its row of the table.
Open profiles
A profile that is open or starting is skipped and named in the message after clearing. In the table it shows "open" instead of the button.
If you start a profile while its cache is being cleared, it opens when clearing ends.
Where the data lives
On macOS the app data lives in ~/Library/Application Support/@armanos/desktop, and the page cache of ARMANOS Browser profiles in ~/Library/Caches/@armanos/desktop.
On Linux these are ~/.config/@armanos/desktop and ~/.cache/@armanos/desktop, on Windows everything is in %APPDATA%\@armanos\desktop.
"Open folder" in the card opens the data folder. If the app was started with --user-data-dir, everything lives inside that folder.
Data without a profile
The line "Data of profiles that are not in the list" appears when cookies and data of profiles that are neither in the list nor in the trash are left on the disk. This happens after a deletion by an older version of the app or after a reinstall.
"Erase" on that line removes them for good, and they cannot be brought back. Profiles in the list and in the trash are not touched by this button.
What this does not do
- It does not set a cache size limit and does not clear the cache on a schedule by itself.
- It does not touch engine components that ARMANOS Browser downloaded itself: they are shown on a separate line.
- It does not clear the cache on another computer: the card counts only this one.
Where this is decided
The weightiest claims and the stand that holds each one.
- The cache, session and component counts match du, the promised amount equals what was freed, cookies and site data stay byte for byte, 200 profiles of 2000 files do not hold the window
- apps/desktop/test/место-на-диске.js
- On both engines: the open profile is skipped and named, the closed one is cleared and opens with the same cookie, a launch waits for clearing to end, "Delete permanently" removes the cache under Caches
- apps/desktop/test/место-на-диске-живьём.js
Questions
- Will I be signed out of sites after clearing?
- No. Cookies and logins stay, only the cache is removed.
- Why does a profile weigh hundreds of megabytes while its session is small?
- Most of it is usually the cache of packages the engine downloaded and the engine components themselves. Clearing removes the cache, the components are shown separately.
- Does "Delete permanently" remove the cache too?
- Yes. Its data and page cache are removed with the profile, including the part that on macOS and Linux lives in the system cache folder.
Try it on your own profiles
The free plan gives two profiles, with no time limit and no card.