Skip to content

Joost Egelie

My feedback

2 results found

  1. 5 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)
    An error occurred while saving the comment
    Joost Egelie commented  · 

    Hi,

    Yes I'm having an external monitor, hooked up with a USB-to-HDMI connector.
    I've tried another resolution, but it didn't show any improvement.

    this is my setup (sorry it's in Dutch, copied from System Information):

    Apple M3:

    Chipsetmodel: Apple M3
    Type: GPU
    Bus: Ingebouwd
    Totale aantal cores: 10
    Fabrikant: Apple (0x106b)
    Metal-ondersteuning: Metal 4
    Beeldschermen:
    iMac:
    Beeldschermtype: Ingebouwde Retina LCD
    Resolutie: Retina 4,5K (4480 x 2520)
    Hoofdbeeldscherm: Ja
    Synchrone weergave: Uit
    Online: Ja
    Pas helderheid automatisch aan: Ja
    Verbindingstype: Intern
    PL2793Q:
    Resolutie: 2560 x 1440 (QHD/WQHD - Wide Quad High Definition)
    Ziet eruit als: 2560 x 1440 @ 60.00Hz
    Synchrone weergave: Uit
    Online: Ja
    Rotatie: Ondersteund

    USB 3.1 Bus:

    Locatiecode: 0x01000000
    Verbindingstype: Built-in
    Driver: AppleT8122USBXHCI

    Belkin USB-C to HDMI Adapter:

    Locatiecode: 0x01100000
    Verbindingstype: Removable
    Fabrikant: Belkin
    Serienummer: 0000000000000001
    Verbindingssnelheid: 12 Mb/s
    USB-fabrikantcode: 0x050d
    USB-productcode: 0x012c
    USB-productversie: 0x0001

    An error occurred while saving the comment
    Joost Egelie commented  · 

    Hi Anmol Sud,

    This setting was the first thing I disabled when I installed Illustrator, so I can confirm the issue is there without that option. RIght now I have an idle Photoshop in the background doing nothing, but using up 107% CPU and 94% GPU. When I'm in Illustrator the GPU gets overloaded and starts throttling.

    Are the new AI functions in the Adobe suite perhaps piggyback-riding on idle processors and GPUs around the world?

    An error occurred while saving the comment
    Joost Egelie commented  · 

    I can confirm the issue is partly an Apple performance issue. The Screenshot app puts extra strain on the GPU when highlighting selected areas in transparent blue., but the rise in use is only around 30% - not the full 100% as Illustrator et al. produce.

    As the problems arose only when I accidentally installed Tahoe on the iMac M3 and persist after every version upgrade of either MacOS X or Adobe apps, I think Adobe can address Apple's unasked-for graphical update "Liquid Glass". I've tried shutting off every visual gimmick in the OS but the problems remain, so I think poorly written and inefficient core frameworks may be the culprit. However, users are not in a position to address this with Apple, but Adobe certainly may have the leverage.

    An error occurred while saving the comment
    Joost Egelie commented  · 

    A very important detail: when I switch Illustrator to Full Screen mode With Menubar, the GPU drops immediately to almost zero (in Dutch: "Weergave > Schermmodus > Volledig scherm met menubalk").
    It's Illustrator (mainly, but also the other Creative Cloud apps) which triggers the Apple Windowserver process into giant GPU loads. But only when it's in standard window mode.

    This is with Illustrator 30.3 on Mac OS Tahoe 26.3.1

    An error occurred while saving the comment
    Joost Egelie commented  · 

    It is still happening. Circumstances are random, but when GPU load runs out to 100% all it takes is hiding all Adobe apps and GPU load drops immediately to about 20%.

    Attached picture is the iMac M3 when all apps are idle; only Illustrator and Apple Mail are open. No graphical tasks are being performed. Again, Windowserver is hogging the GPU.

    An error occurred while saving the comment
    Joost Egelie commented  · 

    Reproducing steps:

    GPU load is always high (like 70% or more) when Illustrator sits idle on screen, when nothing is happening (no drawing).

    GPU load may run up to a constant 100%, with temperatures in the iMac above 100ºC, when other Adobe apps are in the background (like InDesign and Photoshop).

    GPU load drops immediately when Illustrator is "hidden" (i.e. running, but user interface is not on screen). The GPU load drops further with each next Adobe app being hidden.

    An error occurred while saving the comment
    Joost Egelie commented  · 

    When Illustrator is hidden, GPU load drops immediately (iMac M3, only since Tahoe 26.2 was installed).

    By the way, Illustrator gets the fans running top-speed on an Intel iMac with Ventura too.

    For both computers, there are no significant steps to reproduce the problem; the GPU load seems to shoot up randomly, pertaining until Illustrator is closed, or until minutes of inactivity pass, or when Illustrator is hidden.

    Joost Egelie supported this idea  · 
  2. 38 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)
    An error occurred while saving the comment
    Joost Egelie commented  · 

    The solution with the Properties panel is not an improvement: when opening that panel, one STILL has to navigate focus towards the keyboard increment field. What's worse: this can only be done by handling the mouse. Tabbing your way to that field can't be done since [TAB] is the main interface's keyboard shortcut for hiding/unhiding the tool panels.

    Joost Egelie supported this idea  · 
    An error occurred while saving the comment
    Joost Egelie commented  · 

    Since the new update to 29.7.1 the cursor doesn't default to the field Keyboard Increment when pressing [CMD]-K or [CTRL]-K in order to open the preferences dialog. Now it defaults to the (new) search field.

    It hinders flow: typically I use to alter the keyboard increment to different values often on the fly when designing, now an extra grab to the mouse is needed, or tabbing my way through a lot of other fields before I can land focus on the Keyboard Increment field...