Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06814||Misc.||Minor||Always||Jan 1, 2018, 18:28||Jan 1, 2018, 19:46|
|Version||0.193||Fixed in Version||Build|
|Summary||06814: Memory leaks in (SDL) window/video code|
Indirect leak of 3670016 byte(s) in 14 object(s) allocated from:
Indirect leak of 1680 byte(s) in 14 object(s) allocated from:
|Steps To Reproduce|
It appears renderer_sdl1 is never destroyed since sdl_window_info::renderer_reset() is never called when the window is being destroyed (seems also true for the UWP code - Windows code is fine). Also the sdl_window_info::set_renderer() call creates a references to the sdl_window_info shared_pointer causing this object never to be destroyed since the renderer reference still exists.
This leaks will occur each time you run a machine, so the memory consumption will go up the more machines you start from within the UI in one session.
Happens by default on Linux ("-video auto" defaults to "soft" on it) and when using "-video soft" and "-video accel".
|Affected Sets / Systems|
|There are no relationsihp linked to this issue.|
|There are no notes attached to this issue.|