mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #761] Tooks all of the space in the C disk #612
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#612
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @molodchyk on GitHub (Nov 29, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/761
I made one gif and it worked fine. Then, I took the second gif and it started processing it. It stopped and said that there is no free space, although I intended to save it on D disk. It took impressive 20 gigabytes of C disk, and I don't even know where to check to delete this data. Of course, the second gif I was unable to process and save. I cleaned 30 gigabytes of data on C disk, recorded another shot for the second gif, and after processing it shows me again that sign that I don't have free space anymore. Where is all the space? Meanwhile, gif is 3 minutes long.
@NickeManarin commented on GitHub (Nov 29, 2020):
This app was designed to record small clips, in order to save as gif. It's not really optimized to capture long sessions.
You may try to enable memory caching with compression in Options > Recorder, but it won't help much.
Also, to remove the recording cache, go to Extras > Storage and click to clear cache.