c7b1c977f73a665857199895dcbae381715684a1
In gcal_calendar_monitor_init(), self->shared.lock is initialized with g_rw_lock_init(). On Linux/glibc, GRWLock allocates memory for the underlying pthread_rwlock_t (56 bytes). Because g_rw_lock_clear() was never called in gcal_calendar_monitor_finalize(), every finalized GcalCalendarMonitor leaked its lock resources, failing the LeakSanitizer CI build when test_calendar_monitor_expand_recurrences was added. Part-of: <https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/808>
Installation
Links
- Homepage: apps.gnome.org/Calendar
- Report an issue: gitlab.gnome.org/GNOME/gnome-calendar/issues
- Donate: donate.gnome.org
- Translate: l10n.gnome.org/module/gnome-calendar
- Contact: matrix.to/#/#gnome-calendar:gnome.org
Contributing
For information on how to contribute, please check CONTRIBUTING.md and HACKING.md.
Languages
C
97.6%
Meson
1.2%
CSS
0.7%
Python
0.3%
Shell
0.2%
