Memory leaks caused by not destroying wx dialogs #590

Closed
nvaccessAuto opened this Issue Mar 5, 2010 · 1 comment

2 participants

@nvaccessAuto

Reported by jteh on 2010-03-05 08:48
It seems that closing a wx dialog and dropping all references to it is not enough to destroy it. The dialog seems to stay around regardless. This will cause serious memory leaks when many NVDA dialogs are opened and closed. We need to explicitly call Destroy() on dialogs when we're done with them.

@nvaccessAuto

Comment 2 by jteh on 2010-03-07 22:49
Fixed in 9d2a9f4.
Changes:
State: closed

@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2010.1 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment