Closed jwvanderbeck closed 4 years ago
This warrants some thinking about but I'm seeing an increase in memory utilization by about 50,000 KB every time that EDDI's UI is invoked in VoiceAttack.
Possible cause: Event handlers not fully detached prior to closing the window so resources remain in memory and are not released when the window closes. https://social.msdn.microsoft.com/Forums/vstudio/en-US/b2861707-81d6-45d9-853a-11bb9989137a/memory-leak-close-doesnt-dispose-window?forum=wpf
EDDI version in which issue is found
3,4,3
VoiceAttack version in which issue is found (as applicable)
1.7.7
Steps to reproduce
Expected
Repeated opening and closing of the EDDI config screen should not increase VoiceAttack memory usage.
Observed
Each time the EDDI window is opened, more memory is allocated by VoiceAttack that is not released when the configuration screen is closed.
As a result, after a while VoiceAttack/EDDI will start erroring or crashing with an
OutOfMemory
exception. System is not out of memory but it mostly is a local memory allocation that VA or VA plugins are allowed to use?Investigation