Fix #109770: WM: Memory leak of timers for file browser report #109603
|
@ -79,7 +79,6 @@ void BKE_reports_clear(ReportList *reports)
|
|||
report = report_next;
|
||||
}
|
||||
|
||||
MEM_SAFE_FREE(reports->reporttimer);
|
||||
BLI_listbase_clear(&reports->list);
|
||||
}
|
||||
|
||||
|
|
|
@ -606,6 +606,7 @@ void wm_close_and_free(bContext *C, wmWindowManager *wm)
|
|||
WM_drag_free_list(&wm->drags);
|
||||
|
||||
wm_reports_free(wm);
|
||||
BLI_freelistN(&wm->timers);
|
||||
|
||||
|
||||
if (wm->undo_stack) {
|
||||
BKE_undosys_stack_destroy(wm->undo_stack);
|
||||
|
|
Loading…
Reference in New Issue
Timers can themselves have allocated data, this should be replaced by a function which frees timer custom data (see:
WM_TIMER_NO_FREE_CUSTOM_DATA
).Suggest adding
WM_event_timer_free_data(...)
whichWM_event_remove_timer
can call too.