Skip to content

Alec Jacobson

← Adobe Illustrator

My feedback

1 result found

  1. Can't finish previewing. Could not complete the requested operation.

    773 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    464 comments  ·  Illustrator (Desktop) Bugs » Rendering Issues (GPU, CPU)  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Need More Info  ·  Adminaishwarya (Admin, Adobe Illustrator) responded

    Thanks for raising this. We've looked into this issue from our side, but we're unable to reproduce the issue internally so far.

    If you're still seeing it, could you help us with a few details so we can dig in further?

    • Are you still facing the issue? (yes / intermittent / no longer)
    • Machine configuration — OS and version, GPU, and Illustrator version/build
    • Reproduction rate — does it happen every time, or only sometimes?
    • A screen recording of the issue as it happens, if you can capture one
    • The AI file you were working with when the issue occurred (feel free to share a stripped-down/anonymised version if the original is confidential)

    If the issue is 100% reproducible on your machine, we'd be happy to set up a short debug session with you.


    Thanks for your patience and for helping us track this down.


    Warm regards,

    Aishwarya G Gadodia

    An error occurred while saving the comment
    Alec Jacobson commented  · 

    Not sure why this is marked as completed. Updating Illustrator did not help...

    I might have stumbled on a solution when I ran into a permissions issue updating homebrew. The solution was to issue (on the command line via Terminal.app):

    sudo chown -R $USER ~/Library/Caches/

    Suddenly Illustrator started working correctly again. Looks like there was a ~/Library/Caches/Adobe folder that this command was also resetting the permissions of, so maybe that accidentally fixed it. Not sure how the permissions got screwed up. Maybe this is apple's fault (probably!).