You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed this as well but suspect that it's out of my control (for the moment at least). There seems to be either an AppKit or (more likely) PyObjC bug causing a memory leak when drawing to an NSImage context. With every pass through the renderer, a number of internal lock objects are leaked and can add up to significant quantities over time:
I've heard reports that this has been fixed in 10.10.2 but, like you, I'm still on 10.9 so can't say for certain...
Dogg drawing to an NSImage’s NSGraphicsContext will leak like a middle-aged New Orleans alcoholic for reals, it may be in PyObjC but those crazy locks leak anywhere man. If it is NSBitmapImageRep-backed it will also sometimes (non-deterministically) leak the entire image buffer when the NSImage releases.
Although yeah actually that screenshot also shows a leak from a PyObjC strdup() wrapper, what? You don’t tell people you use strdup() much less proudly wrap it with a conspicuously named API call. That’s the POSIX equivalent of starting a conversation with friends by telling them you haven’t changed your socks in a week. Absolute leaksville.
Activity
samizdatco commentedon Jan 19, 2015
I've noticed this as well but suspect that it's out of my control (for the moment at least). There seems to be either an AppKit or (more likely) PyObjC bug causing a memory leak when drawing to an NSImage context. With every pass through the renderer, a number of internal lock objects are leaked and can add up to significant quantities over time:
I've heard reports that this has been fixed in 10.10.2 but, like you, I'm still on 10.9 so can't say for certain...
ifmihai commentedon Jan 21, 2015
maybe, there will be someone with at least 10.10.2 that will tell us :)
or maybe i will update to 10.10.2 when it will be available
I tried to avoid updating to yosemite as long as possible
fish2000 commentedon Oct 8, 2015
Dogg drawing to an NSImage’s NSGraphicsContext will leak like a middle-aged New Orleans alcoholic for reals, it may be in PyObjC but those crazy locks leak anywhere man. If it is NSBitmapImageRep-backed it will also sometimes (non-deterministically) leak the entire image buffer when the NSImage releases.
Although yeah actually that screenshot also shows a leak from a PyObjC
strdup()wrapper, what? You don’t tell people you usestrdup()much less proudly wrap it with a conspicuously named API call. That’s the POSIX equivalent of starting a conversation with friends by telling them you haven’t changed your socks in a week. Absolute leaksville.