More > JRiver Media Center 27 for Mac
Thumbnails taking up a lot of disk space
MrBiff:
Providing Free space information for a copy on write file system is very challenging.
There are more relevant articles at the site. Search Finder.
Captain_Bitter:
OK, so a couple updates:
1. This is definitely a bug. Not necessarily a JMRC-initiated bug, but a bug with how JMRC interacts with MacOS.
2. This bug impacts both 'Thumbnails (large).jmd' and 'Thumbnails (medium).jmd'. At first, I thought it only impacted the 'large' file, but that's only because the 'medium' file is smaller to begin with....so the file bloat doesn't impact the totals as much. But it definitely is both files impacted.
3. The bug causes the (in my case) 2GB thumbnails (large) file to take up an increasingly big amount of disk space. Creating 100k thumbnails drove this file to 75GB, and the applications storage (seen in System Settings > General > Storage) to 125GB!!
4. The thumbnails files seem to be the only files impacted.
5. Once the storage problem is created, all I can do is wait until the OS retrieves the errant disk space. I thought I could do something by going to Storage, but I was incorrect on that.
6. Although I have an older version (JMRC27), unless thumbnails are created differently in subsequent versions (doubtful), this problem is likely to persist up until the latest version.
7. This may be a MacOS issue, but it does not impact other apps that I have seen. I am demoing another music playing app right now, and this effect is not seen in that app -- file sizes in bytes and the disk space requirements are identical.
For me, it means I need to create as many thumbnails at a time as my disk space can handle, stop, quit JMRC and wait for a "cooling off period" for MacOS to recover the disk space.....then restart thumbnail creation. I estimate I will have to repeat this process at least 20x to get all the thumbnails created. And, once I do, I better not have cause to recreate the database or else this problem repeats itself. Once I let the disk space get down to about 20GB free (too low), everything slows down on this system. I have yet to determine how was down I can drive the disk space before performance is impacted.
I'd be interested if anyone else has seen this issue with JMRC. Additionally, if anyone on the development side is planning to look into this, I would be happy to provide database files, etc. for testing/debug purposes. At present, I have been waiting about an hour for the "incorrectly gobbled up disk space" to free up, with no end in sight. So creating all the thumbnails may take me well past this weekend, assuming I am diligent about checking the disk space regularly.
Regards, Dave
P.S. Looking into the APFS Snapshot issue, when I go into the Disk utility, the option to "View Snapshots" is greyed out. I believe that means I only have one snapshot, so it is unclear if this is part of (or related to) the issue/bug I have outlined above. If it is related, having one Snapshot means I can't do anything to correct this issue by deleting previous Snapshots, so this isn't a solution for me.
Captain_Bitter:
Well, this frees up the "frozen" space.
Reindex Apple Spotlight
When the Apple Spotlight index is corrupted, macOS may display the free space improperly in Finder. To get rid of this issue, you can reindex Spotlight with The Terminal command. This solution also works when you can't search an external hard drive on a Mac.
Choose Apple menu > System Settings.
Click Siri & Spotlight in the sidebar, then scroll down and click Spotlight Privacy on the right.
Click the add button (+) and select the disk to add.
Select the disk that you just added. Then click the remove button (–) to remove it from the list.
Click Done, then quit System Settings.
The drive's contents will be reindexed by Spotlight. Depending on the volume of information being indexed, this can take some time.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
I can attest that this works. Once the drive was reindexed, I got the space back right away.
JimH:
This is probably an Apple bug.
Your steps above probably cause the OS to do "garbage collection".
Captain_Bitter:
--- Quote from: JimH on January 26, 2024, 01:15:27 am ---This is probably an Apple bug.
Your steps above probably cause the OS to do "garbage collection".
--- End quote ---
No doubt. But the question wrt JMRC is: what is it about Thumbnail creation that causes the MacOS "garbage collection" (or "garbage creation") to go off-the-rails? It doesn't happen when loading files. It doesn't happen when playing. It doesn't happen with any other app I use on this machine.
So there *IS* something about Thumbnail creation that causes this issue....in conjunction with a likely MacOS issue. What I am wondering is if there something about Thumbnail creation that could be modified so the problem doesn't occur. For example, is Thumbnail creation designated as purgeable/non-purgeable space within the app? I don't know what the answer is, merely asking if this could be done in a different way.
Note: even after the previous referenced action to recover space, when I look at the Thumbnails folder, it still shows 2.95GB....and nearly 74GB "used".
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version