Track tasks and feature requests
Join 36 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesMemory leaks caused by not destroying wx dialogs #590
Comments
This comment has been minimized.
This comment has been minimized.
|
Comment 2 by jteh on 2010-03-07 22:49 |
nvaccessAuto
added
bug
NVDA GUI
memoryLeak
labels
Nov 10, 2015
nvaccessAuto
assigned
jcsteh
Nov 10, 2015
nvaccessAuto
added this to the 2010.1 milestone
Nov 10, 2015
nvaccessAuto
closed this
Nov 10, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nvaccessAuto commentedMar 5, 2010
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.