Copy link to clipboard
Copied
Hi There,
I have been using Illustrator CC2021 just fine on Mac Big Sur 11.2.1 since both were released. I have 3 AI files that a designer sent me, all around 60-90Mb file size. Two of them open fine. I can zoom in/out, edit, all normal. The third I open successfully. If I drag the canvas around it's fine. If I zoom in, try to edit, or do anything it causes a memory leak. Illustrator locks up and the Illustrator processes climbs from about 3GB up to 130GB when my system runs out of swap file drive space.
MacBook Pro Late 2013 -- 2.3 GHz i7 -- 16GB -- 500 GB SSD -- NVIDIA GeForce GT 750M 2 GB
This is not a system resource issue it's something else. I tested on another MBP 2016 with 16GB and similar resources running CC 2021 on current version of Catalina.
Using Illustrator for anything else works fine. Tried Save As as an Adobe PDF, same issue. I saw issues in 2016 with similar issue and deleted Library > Application Support > Illustrator 25 and Library > Preferences > Illustrator 25, did not fix issue.
Anyone else seen this before, ideas what is happening here? Thanks!
UPDATE - It is actually not the GPU, it is the Preferences > Performance > GPU Performance setting that is cauing the memory leak on this file. I tried turning off Animated Zoom which did not fix the issue. I tested turning off GPU Performance on both MacBook Pro's one with NVIDIA one with only Iris Pro. Both systems had the issue, but resolved when GPU Performance was disabled.
Copy link to clipboard
Copied
SOLVED - I turned off support for the NVIDIA GeForce GT 750M 2 GB video card and used just the onboard Iris Pro, works fine. Adobe, looks like there is an bug / issue here.
Copy link to clipboard
Copied
UPDATE - It is actually not the GPU, it is the Preferences > Performance > GPU Performance setting that is cauing the memory leak on this file. I tried turning off Animated Zoom which did not fix the issue. I tested turning off GPU Performance on both MacBook Pro's one with NVIDIA one with only Iris Pro. Both systems had the issue, but resolved when GPU Performance was disabled.