After WorkBuddy ate 10GB of disk, I finally understood its memory bill

Last Wednesday afternoon, I was rushing to finish a course paper in my dorm when my computer fans suddenly started spinning like crazy. I opened Task Manager and saw WorkBuddy hogging 1.8GB of RAM, with the C drive's available space dropping from 40GB to 12GB. I was a bit confused—I remembered it working fine just yesterday. Out of curiosity, I checked Resource Monitor and found that C:ProgramDataWorkBuddy plus .workbuddy in the user directory added up to over 10GB. Coincidentally, around those days I came across a CSDN article titled "Optimizing WorkBuddy Model Memory Usage: From Memory Hog to On-Demand Loading." After reading through it and checking out other posts about WorkBuddy's disk usage, I finally figured out where all the space went.