Skip to main content
Joehogeye
Joehogeye
Participating Frequently
February 20, 2019

P: Character Panel causes instant crashes

  • February 20, 2019
  • 15 replies
  • 321 views

Ever since upgrading to PS v20.0.0 I have experienced crashes when clicking on the font selector in the character panel. I am currently on 20.0.3 and still having the same issue.
I went through all of the troubleshooting steps of validating my fonts, running the "Font Test" script, and deleting potential problem fonts from my system.

The problem is that the crash is not fully repeatable. It doesn't really matter what I am doing leading up to the crash, it just seems random. For the most part the character panel works fine, but at least a few times a week I will get it to crash. My only thought is that I am using a Wacom stylus when clicking on it, but that seems unlikely.

Has anyone experienced this kind of issue before? Or is this a new bug in v20? I've gotten to the point of saving my file before I change any font due to its frequency.

    This topic has been closed for replies.

    15 replies

    J
    J453
    Legend
    January 19, 2022

    Fixed in 20.0.5 or later.

    David Mohr
    David Mohr
    Participating Frequently
    April 8, 2019
    Howdy Joe,

    Thanks for the update.  Fingers crossed, that the setting change to Legacy Compositing fixed it.

    Thanks again,
    David
    Joehogeye
    JoehogeyeAuthor
    Participating Frequently
    April 8, 2019
    It wasn't a particular file that would trigger the issue.
    Also, a crash has not occurred for a few weeks now. I'm not sure if toggling on Legacy Compositing fixed my problem, or if the changes made in update 20.0.4 made a difference.
    A
    Andrew_Sender
    Participating Frequently
    April 8, 2019
    Hi Joe,
    Could you possibly email me (sender@adobe.com) the PSD file you're working on where Photoshop randomly crashes?  I've been trying to investigate this issue for a while and appreciate any help I can find. 
    Joehogeye
    JoehogeyeAuthor
    Participating Frequently
    March 5, 2019
    David,

    I've gone the last few work days without a single crash. Out of curiosity, I switched off Legacy Compositing this morning to see if it would crash again. Sure enough, here a few hours later it crashed on me again. For whatever reason, I wasn't given a report window popup from Photoshop. The Apple window come up, but not the Adobe one I can send to you.

    Also, something interesting that I've noticed is that Legacy Compositing is now checked back on after re-launching the program.
    Joehogeye
    JoehogeyeAuthor
    Participating Frequently
    February 25, 2019
    I've now turned on Legacy Compositing. I'll see what happens and keep you updated.
    David Mohr
    David Mohr
    Participating Frequently
    February 25, 2019
    One more thing, Joe.  I was talking to a developer and I want to rule this out as well.

    Please got to Preferences > Performance and at the bottom of the dialog, under Options, there's Legacy Compositing.  Is that unchecked?  If so, try checking it and see if the problem disappears.  I would love to hear either way.

    Thanks,
    David
    David Mohr
    David Mohr
    Participating Frequently
    February 25, 2019
    Awesome.  Thanks, Joe.  I'm hoping that solves it, but I have a bug ready if it doesn't.  8-)

    If you crash again, definitely put my name in your report.

    Thanks,
    David
    Joehogeye
    JoehogeyeAuthor
    Participating Frequently
    February 25, 2019
    David,

    I have deleted the CT Font Cache folder (from the trash as well), and then ran the command to delete the OS cache from the terminal. I have done so with all adobe applications closed.

    I will let you know if the program crashes again after clearing all caches.

    Thanks!
    David Mohr
    David Mohr
    Participating Frequently
    February 25, 2019
    Howdy Joe,

    Thanks.  Please let us know if clearing the font cache, both the Photoshop AND OS cache (otherwise, they can re-corrupt each other).  Installing fonts and even some poorly-made fonts can corrupt the caches.  Clearing them both caches would address this -- I need this ruled out before I pass it to developers.

    Thanks,
    David
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices