-
-
Notifications
You must be signed in to change notification settings - Fork 159
Description

marp-cli version:
marp.exe 4.x.x
Problem Description:
On Windows 11 systems, marp-cli creates numerous temporary folders (named "marp-cli-xxxxx" with random suffixes) in the user's Temp directory. Each folder occupies approximately 18MB of disk space.
In my current workflow, I need to execute marp commands in bulk through the software, which generates these temporary files with each execution. After just 10 days of operation, these temporary files have accumulated to over 400GB on my C: drive, which is concerning for both storage space and system performance.
Questions:
-
Cleanup Process: Are these temporary folders meant to be cleaned up manually, or is there an automated cleanup mechanism that should be handling them?
-
Optimization Possibility: Is there any way to prevent or minimize the generation of these temporary files? Considering that each marp command execution (producing just one PNG image) corresponds to an 18MB temporary folder, the current implementation creates significant disk I/O:
• This frequent disk activity may impact system performance• The constant read/write operations could potentially reduce SSD lifespan
• Would it be possible to implement an in-memory solution for these temporary files instead of writing to disk?
Additional Context:
• Temp directory location: C:\Users[username]\AppData\Local\Temp\
• Each temporary folder is consistently ~18MB in size
• High volume usage scenario: bulk processing of marp commands
• Visible impact: 400GB+ accumulation within 10 days