The Problem of PicGo Log File Becoming Too Huge
Few days ago, I found the C drive storage space of my computer (Windows system) suddenly lost over 60 GB. The first thing came to my mind was that there were too many temporary files generated during use. So, I cleaned the C drive using built-in system tool1, but it didn’t work.
Later on, I thought perhaps it’s because there were too many cache files for a certain program, and the Windows system can’t recognize them according to the rules. I firstly guessed the program is Typora, because I always use it to write blogs and I remember that, although I set to upload inserted images to GitHub repo2 via PicGo3, Typora still make a backup for the image locally every time. So, I found the image storage directory4, C:\Users\<user_name>\AppData\Roaming\Typora\typora-user-images, but its size is only 126 MB.
Note: The folder C:\Users\<user_name>\AppData is a hidden folder.
Although it’s not caused by Typora, the direction was correct. So next, I sorted files and folders in the directory C:\Users\<user_name>\AppData\Roaming\ by Date and check them one by one. And luckily, I found a very huge folder, C:\Users\<user_name>\AppData\Roaming\picgo with size 283 GB. This folder stores the cache files of aforementioned PicGo, and under this folder, there is a single file picgo.log, whose size approaches 283 GB. It is the reason! It is the log file of PicGo, and its problem of occupying too many storage space is a bug which others ever reported5.
I feel very comfortable after deleting this mega file 😁 And it doesn’t affect the subsequent image uploading.
By the way, in the last two or three months, my computer at times encountered the blue screen of death, and then it would restart instantly. This process always happened so fast that I couldn’t write down the error code. Right now, I guess probably this problem is also attributed to the above PicGo bug. I’ll see in future if the guess is right. (Jan. 09, 2025: Regretfully, the answer is not 😑)
References