I have a long running application that accumulates an apparently unlimited number of CVDisplayLink threads. I do not have a test case.
Enclosed is a process sampling. I can provide a Metal trace, but the file is too large to attach.
The application was run on an M2 system and macOS 13.6.
The problem could be caused by threading issues. The startDisplayLink and stopDisplayLink methods of the Objective-C class MTLLayer are invoked on multiple threads. They are invoked on the AppKit main thread from screen sleep notifications and blitTexture. They are invoked on the EDT from MTLLayer.validate. They are invoked on the Queue Flusher thread from MTLRenderQueue.flushBuffer.
Enclosed is a process sampling. I can provide a Metal trace, but the file is too large to attach.
The application was run on an M2 system and macOS 13.6.
The problem could be caused by threading issues. The startDisplayLink and stopDisplayLink methods of the Objective-C class MTLLayer are invoked on multiple threads. They are invoked on the AppKit main thread from screen sleep notifications and blitTexture. They are invoked on the EDT from MTLLayer.validate. They are invoked on the Queue Flusher thread from MTLRenderQueue.flushBuffer.
- relates to
-
JDK-8312198 [macos] metal pipeline - window rendering stops after display sleep
-
- Open
-