| Search: Advanced search | Contact Us |
Loading
Browse Categories:
|
|
I imported a collection of fonts and I am seeing a process called Profile Agent Crash repeatedly. What is going on? |
|
|
If you import
a lot of fonts (usually in the thousands) this import can take several minutes and the Profile
Agent could encounter dozens of fonts that it finds corrupt. Each time this occurs the ProfileAgent will crash. This crash is harmless and is expected behavior.
The crash report and console logs usually indicate ATS encountered corrupted fonts for bad cache data. So there a couple options. You can make sure your caches are cleared on a regular basis. Bad caches will exacerbate this issue. Also, you can choose to remove the font in question. When a font fails to profile, it is marked with a red "x" in FAP and you can remove it. This issue you are seeing will appear when you are initially profiling your fonts, and if you have a large collection chances are you will have several fonts that fail the profile process. This is normal behavior. Once the initial profile process is done, you should not see the issue again unless you decide to once again profile your font collection. |
|
Powered by
KBPublisher (Knowledge base software)