curious about `passRetained` in event tap callback about keyboard

[godbout]

i can die peacefully in my sleep now \o/

thanks again for your time.

[creasty]

I hate to break it to you but I'm no expert either. This has been the first and only macOS app I've ever created so far.
Perhaps, the simplest reason as to why passRetained being used here is that I found an implementation that used passRetained and I didn't give it much thought...

For what it’s worth, I have never had a memory issue — Consumption-wise, it only uses 15MB at a startup and a week later.
So I assume it might not be critical if we use passRetained or somehow it releases memory at some point. 🤷‍♂️

Anyway, now that you've mentioned it, I've tested both versions and examined the memory usage.
The below are the result of Instruments where I waited 10 sec after the startup, pressed as many random keys as possible for 30 sec, and waited another 20 sec to stop.

passUnretained

passRetained

You're right, there were actually memory leaks.
Wonder how it hasn't been a problem for me...

[godbout]

ah. thanks for taking the time. and sorry, i meant no macOS/iOS/Swift/Objective-C development here.

i've heard about Instruments but haven't open it yet. seems another big chunk of time and exploration needed to understand that one correctly too. but i'm confused—again—now with your screenshots. i would have expected the leaks to appear on the passRetained one rather than the passUnretained? actually, if passRetained doesn't show any leak, i would have expected passUnretained to simply crash. so, am i misunderstanding how Instruments is reporting leaks?

btw. thanks for making this repo public. inspiring, beautiful code.

[creasty]

but i'm confused—again—now with your screenshots. i would have expected the leaks to appear on the passRetained one rather than the passUnretained?

Oh, shoot. It was the other way around. Swapped the titles.

btw. thanks for making this repo public. inspiring, beautiful code.

My pleasure.