---
title: "The Day 48 Gigabytes Stopped My Computer"
canonical: https://dxdev.com/blog/2026-05-23_day-48-gigabytes-stopped-my-computer/
datePublished: 2026-05-23
---
The screen froze solid on May 23, with no space left on the drive Windows needs to run. Nothing responded. I forced a restart and, once the computer came back, began dragging temporary files off the C: drive by hand. I was not cleaning up because I felt organized. I was trying to make enough room to open a terminal and find out why the machine had stopped.

At first, I expected the answer to be boring log files. That is where I went looking. I did find a few things worth moving. Shifting one application's stored data off the system drive and removing programs I had not opened since January freed about 4 GB. It was useful. It was also not nearly enough to explain a computer that had run out of room.

The real answer was a folder holding Chrome profiles. It was 48 GB.

A browser profile is just a separate folder of browser stuff. It can hold the bits that make a browser feel familiar, such as the pages it remembers, its saved website state, and other leftovers from a visit. In this case, browser automation had been running for months. Every session that needed a browser got its own fresh profile. That part made sense. A clean profile helps keep one session's sign-ins and leftovers from spilling into another session.

The problem was not the fresh start. The problem was what happened after the session ended.

There is a technical word for this, and it is worth knowing once: **lifecycle**. It simply means the full life of something, from when it is made to when it is cleaned up. I had planned the beginning. Each session got a separate place to work. I had not planned the ending. No one had told those folders when to go away.

Chrome is not a small guest. Even a short browser run can add a few hundred megabytes to a profile. That is like putting a few heavy grocery bags in a closet every time someone stops by, then never opening the closet again. One bag does not matter. Months of bags do. Nothing failed while those profiles were growing. The automation worked. The sessions finished. The folders simply stayed where they were, getting bigger until the C: drive was full and Windows had no room to breathe.

The first cleanup cost time and patience at the worst possible moment. It was manual work done only to get the computer usable enough to investigate. The 4 GB I found bought breathing room, not a fix. The important discovery was that I had built a careful wall between sessions without giving the abandoned pieces a way to leave.

I changed two things.

First, I stopped making a new browser profile every time. There are now 25 numbered slots. A browser session borrows one, does its work, and gives it back. When it comes back, the slot is reset. The browser's clutter is cleared, while sign-in information that is meant to remain can be kept. The key point is simple: there can only ever be 25 of these folders, no matter how many sessions run over time.

Twenty-five was not a magic number. I usually had four or five browser sessions going at once, so 25 gave room for more without making the pile endless. If that number turns out to be wrong, it can change. What matters is that the number is visible and limited. A drawer with 25 spaces cannot quietly turn into a warehouse.

Second, those browser folders moved off the system drive and onto a separate data drive. That change matters even if the cleanup plan works perfectly. The system drive is the floor under the whole house. If it fills up, the computer can freeze. A data drive can still get full, and that is a problem, but it does not have to bring the operating system down with it.

After the cleanup and the move, I recovered 52 GB. The computer went from frozen solid to comfortable again. I also wrote down two follow-up jobs. One was to make borrowing a browser slot simple, so nothing has to guess which number to use. The other was to look for other folders that might be growing quietly in the same way.

That last part may be the most useful lesson. A warning that says "disk full" tells the truth, but it does not always tell the whole story. The deeper question is whether something is being created over and over without a plan for what happens when it is finished. A cleanup day every few weeks may make the room look better. It does not fix the habit of leaving the bags in the closet.

The fix had two numbers in it. Browser work now borrows one of 25 numbered slots and returns it reset, so the folders can never outgrow 25, and those slots sit on a separate data drive so a full folder cannot freeze Windows again. The cleanup and the move recovered 52 GB, and the cause was a 48 GB folder of profiles that nobody had told when to go away.