Skip to content

/nvda

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Memory leaks caused by not destroying wx dialogs #590

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

Memory leaks caused by not destroying wx dialogs #590

nvaccessAuto opened this issue Mar 5, 2010 · 1 comment
Assignees
@jcsteh
Labels
NVDA GUI bug memoryLeak
Milestone
2010.1

Comments

@nvaccessAuto
Copy link

@nvaccessAuto nvaccessAuto commented Mar 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.
@nvaccessAuto

This comment has been minimized.

Sign in to view
Copy link
Author

@nvaccessAuto nvaccessAuto commented Mar 7, 2010

Comment 2 by jteh on 2010-03-07 22:49
Fixed in 9d2a9f4.
Changes:
State: closed
@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
Assignees

@jcsteh jcsteh

Labels
NVDA GUI bug memoryLeak
Projects
None yet
Milestone
  2010.1
2 participants
@nvaccessAuto @jcsteh
You can’t perform that action at this time.