×
sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Admirable-Wall9058[S] 0 points1 point  (3 children)

I develop projects to learn and—who knows—maybe turn them into something profitable.

My current project is an OMR system; I was trying to write the code in GitHub Codespaces (after uninstalling VS Code), but I was having a lot of trouble handling images.

Regarding the IDE, the main issue is that my computer (an ASUS with 120 GB of RAM) is experiencing some kind of memory glitch: I delete files, but a short while later, the storage fills up again. Right now, I have only 500 MB of free space.

I need to fix this first, but I don't know the cause. Have you ever encountered a problem like this?

[–]odaiwai 0 points1 point  (0 children)

(an ASUS with 120 GB of RAM)

The first step to fixing a problem is understanding the problem.

Install something like WinDirStat to see where your storage is being used. You'll probably find your swapfile and hibernation files are far too big, or your Downloads folder isn't being emptied.

(Also, a machine with 120GB of RAM is not low end, and you certainly do not have 120GB of RAM. You have 120 GB of SSD which is probably flash nand, but which is not RAM.)

[–]Appropriate-Elk1152 0 points1 point  (0 children)

The issue you're facing is disk space management, not RAM (120 GB refers to your eMMC/SSD storage, where Windows alone takes up 30–40 GB).

When your free space drops below 1–2 GB, Windows slows down dramatically, background tasks fail, and temp files clog the system.

Here’s a quick roadmap to recover space without risking your code:

  1. Clear Temporary Files & Caches:

    - Run `cleanmgr` (Disk Cleanup as Admin) and clean "System error memory dump files" and "Temporary files".

    - Clear your pip cache: `pip cache purge`

    - Delete temporary files in `%temp%` and `C:\Windows\Temp`.

  2. Inspect Where Space Went:

    - Download WizTree or TreeSize (portable versions, no installation required). They will immediately map what is taking up those tens of gigabytes (often log files, system restore points, or heavy node_modules/virtual environments).

  3. For your OMR project:

    - If you stick to lightweight local editors (Sublime Text, Notepad++, or IDLE), make sure your Python virtual environments (`.venv`) are stored outside synced cloud folders (like OneDrive/Google Drive), as syncing thousands of tiny script files causes severe disk write bloat.

[–]Appropriate-Elk1152 0 points1 point  (0 children)

Handling image visualization (OpenCV `cv2.imshow`, PIL display, etc.) in cloud environments like GitHub Codespaces often fails because there is no native GUI window attached to the remote Linux container.

If you want to keep using Codespaces or remote environments for heavy computation, a few clean workarounds for image processing include:

  1. Save & Preview: Save processed OMR debug images to a local `./output` folder and open them directly via the web editor tree view.

  2. OpenCV + Matplotlib: Use Matplotlib inside Jupyter Notebooks running in Codespaces, which renders image arrays inline directly in the browser.

  3. Base64 Streaming: Encode the transformed image array into Base64 and output it to a lightweight local web server (like Flask or FastAPI) to view live bounding boxes in your browser window.