Thanks for submitting the crash report and letting us know. However, to maintain the privacy and security of our community members, we ask that personal details not be shared publicly. I have removed your email from your reply. Before doing that, I made sure to share it with @Douglas_Waterfall internally.
I found one crash report from you so far - they sometimes are hard to find - marked May 24, 10:34 AM, and you on Windows 10.0.19045 and AE 23.4(53).
The one I am looking at is not strictly what I would consider a startup crash - assuming I am reading it correctly - the call stack looks like a font is being applied and it crashed.
Does that tie into something you were doing? If so, what font were you trying to apply?
No, it does not apply at what I was doing. It seems that disabling Adobe Fonts in CC solves the problem. But if I want to use Adobe Fonts in the future. How can I fix it?
Good! Now we gotta figure out what font is causing the conflict/crash.
Typically this comes from duplicates - the next version does a much better handling of that.
I have no idea how many fonts you had activated - the hard way would be to re-activate them one by one and re-launch hoping to reproduce the crash.
An more efficient strategy would be re-activate half of them, then try to launch - if it crashes, then it is somewhere in that set. Then you de-activate half of the ones you activated and try again. That will limit how many tries you have to do.
Annoying, but sometimes there is no more efficient way.
13
Replies
AdChoices
