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
this crate is being used in hackclub/kicad-wakatime, which has been suffering a memory leak for quite some time (tracking issue kicad-wakatime #3). using the Instruments tool on macOS, i've finally isolated the leak to this crate.
kicad-wakatime needs to call get_active_window() repeatedly, which leads to the leak.
i am not sure if the memory leak is present on other operating systems, but on macOS, users have reported potential memory usage of up to 30GB after a few hours.
The text was updated successfully, but these errors were encountered:
CFRelease(window_list_info as CFTypeRef) is not called there - it's only called when the crate is about to return Err(()). add a CFRelease() call just above return Ok(active_window), and the leak is no longer reproducible.
sporeball
added a commit
to sporeball/active-win-pos-rs
that referenced
this issue
Dec 19, 2024
this crate is being used in hackclub/kicad-wakatime, which has been suffering a memory leak for quite some time (tracking issue kicad-wakatime #3). using the Instruments tool on macOS, i've finally isolated the leak to this crate.
kicad-wakatime needs to call
get_active_window()
repeatedly, which leads to the leak.i am not sure if the memory leak is present on other operating systems, but on macOS, users have reported potential memory usage of up to 30GB after a few hours.
The text was updated successfully, but these errors were encountered: