Skip to content

Simon

My feedback

1 result found

  1. 773 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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
    Simon commented  · 

    I performed the test that Ashutosh suggested, and anecdotally it does seem to have some effect – after half an hour or so it was still OK – certainly not happening instantly like it was before.

    iMac (Retina 5K, 27-inch, Late 2014)
    4 GHz Intel Core i7
    32 GB 1600 MHz DDR3
    AMD Radeon R9 M295X 4096 MB

    An error occurred while saving the comment
    Simon commented  · 

    Since upgrading from CC 21.1.0 (2017) to CC 23.0 (2019) I am getting constant memory errors, including "Can't finish previewing." and "The operation cannot complete because there isn't enough memory (RAM) available.

    This issue is new to 23.0 and wasn't there in 21.1.0.

    I'm on an i7 iMac 5K with 32GB RAM running Mac OS 10.14.

    Going to have to downgrade back to 2017 until this issue is resolved.

    Simon supported this idea  ·