v7.12.4Stable
Unused browser downloads removed from the server
The server was holding four spare copies of a browser that nothing on it was using. We checked that first, then removed them and freed 1.2 GB. No linked number was disconnected and the service was not restarted.
Highlights
- Four unused browser downloads removed, 1,235 MB in total
- Disk in use went from 23.9 GB to 22.7 GB
- None of them had been opened in the last 30 days
- No restart, and the number that was online stayed online
- WhatsApp login data was not touched
In this release1
- ImprovedSystem
Four spare browser copies removed
Each linked WhatsApp number runs in a browser on our server. That browser is installed once, system wide, and it is the one every session uses.
Separately, one of our software libraries had downloaded its own copies of a browser, two versions in two forms each, in January and July this year. They were never put to use and were simply taking up space.
What we checked before removing them:
- The service is configured to use the system browser, and that is the only place in our code that starts one.
- Every browser process running at the time came from the system browser. None came from the spare copies.
- No file in the spare copies had been opened in the last 30 days.
What we did:
- Removed the four copies, 1,184 files and 1,235 MB in all.
- Checked straight afterwards: the service was still running without a restart, the number that was online was still online, and the public API answered normally.
api 7.12.4