CoreML folder size issue on Mac | 100+GB

Topaz Photo Bugs and Issues
1

I used the support submission form but thought I would ask here as well.
I’m running MacOS Sequoia 15.6.1 on a MacBook Pro with M3 Pro chip.

There seems to be a persistent problem with installing unnecessary coreMLCache with the models, filling my disk.

I allowed Topaz Photo AI to install Topaz Photo. The downloaded models included coreMLCache which was about 215 GB in size! This occurred with v1.0, v1.0.4, and v1.1.1. The sharpening model failed to run.

There is a tech note stating to “reset” coreMLCache. I knew that meant to delete it, but the note isn’t clear what to do.

The documented minimum and recommended requirements state 20 GB. The actual impact was about 217 GB. This is unacceptable.

By testing each Sharpening model, I found that the Wildlife Beta is the culprit. I suspect there is a bug in how TP is calling CoreML, somehow causing a loop which loads up cache until the disk fills.

Anyone else seeing this?

2

On Mac, I think there is a “Clear Model Cache” option in the Help menu of the app.

3

I don’t see anything like that anywhere in the menu tree.

4

The log includes repeated entries of “Info | [AIE] Can’t read file in zip /Applications/Topaz Photo.app/Contents/MacOS/../Resources/models/sstd_ahres-v1-fp32-512x512-mlc.tz” until I force quit the app.

5

Bit surprised that Photo doesn’t have the same option as Gigapixel, but maybe the GP option is different.

Anyway there are some instructions given in the thread below:

6

I know how to delete it; that’s not the point. They need to fix the bug to prevent it from filling my disk.

I am working an open issue with Topaz support.

7

We will reach out if any fixes are found by the development team and have added your contact information on the development team ticket created for this issue. We don’t have any other reports for this, and no other reports at the moment, where the deletion does not fix this, and it may not be something we can fix on your machine only. We will reach out on the email you sent if any further steps from the development team or a fix is found!

1 Like
9

I have seen some suggestions - not confirmed - that problems like this could be specific to the Apple M3 processor. Just something to check out, if the team is trying to duplicate it.

Let me know if the team wants me to capture any logs or other info next time they want me to test a fix.

Thanks.

1 Like
10

Thanks. We will be discussing this furthermore with the development team tomorrow. We will reply on the email thread we have if any further steps to test of other logs needed!

1 Like