Yamada Taro
My feedback
1 result found
-
4 votes
The team has been able to reproduce the issue and are further debugging the issue, intending to push a fix soon.
An error occurred while saving the comment
I would like to add profiling evidence from Illustrator 30.8.2 on macOS 15.7.3, running on an Apple silicon Mac Studio. My workflow involves a document with many linked PSD images on an external APFS volume.
In one session, memory stayed around 1.3–1.4 GB for roughly 70 minutes after launch. Around the time I opened the document, it rose to approximately 3.1 GB. After an initial fluctuation, logged memory readings increased at roughly 2 GB per hour. A sample taken about 5 hours 20 minutes after launch reported a physical footprint of 10.1 GB. These figures come from different logging tools and rounded displays, so they are approximate.
Later, when no document windows were visible and I believed the document was closed, memory continued to increase. A filesystem trace recorded a specific Illustrator thread accessing PSD paths referenced by that document. I have not verified whether Illustrator still retained an internal document object. The saved document metadata contains 210 distinct PSD references, but the short trace does not establish that all 210 were accessed.
In a five-second sample, this thread was sleeping for approximately 97% of its observations. The active branches included file-existence checks, URL-resource queries and display-name lookup. One branch in the Illustrator executable was:
0x19d61dc → 0x19d5544 → 0x19d4eb4 → 0xf17c98 → 0xf17e10 → @objc _NSFileManagerBridge.displayName(atPath:)
The same relative offsets appeared in an earlier sample from the same Illustrator version while documents were open. In the later trace, the filesystem thread identifier matched the thread in the sample. Calls included stat64 and getattrlist on PSD files and their parent directories.
In a separate overnight session, vmmap showed increasing numbers of allocated small blocks in MALLOC_NANO and MALLOC_TINY. Total allocation counts rose from approximately 7.5 million to 105.3 million, while allocated bytes rose from 1.9G to 23.5G over about ten hours. This is a net increase in outstanding allocations, not a count of every allocation operation.
The evidence suggests that file-reference monitoring may remain active after document windows close. I have not established that this thread owns the growing allocations, or that it is the same root cause as the original report. Restoring the external device's USB 3 connection did not stop the observed file checks.
Could the team check whether this relates to the issue already reproduced here, and whether there is a supported workaround that stops the growth without quitting Illustrator? I can provide sanitized sample, filesystem-trace and vmmap excerpts. I will remove confidential filenames and paths before sharing them.