Skip to content
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

Possible bug with XtDestroyWidget in main.c and messages_gui.c #97

Open
we7u opened this issue Apr 25, 2019 · 0 comments
Open

Possible bug with XtDestroyWidget in main.c and messages_gui.c #97

we7u opened this issue Apr 25, 2019 · 0 comments
Assignees

Comments

@we7u
Copy link
Member

we7u commented Apr 25, 2019

This looks related to bug #88. I ran through all of the C-code looking at where XtDestroyWidget was used, then checked whether there were associated callbacks that might still hang around. These two files need a more detailed look to determine whether XtRemoveCallback() may be warranted before the XtDestroyWidget() calls:

main.c: Line 9759
messages_gui.c: Code associated with mw[i]

Note that there may be TWO LEVELS of callbacks in main.c:BuildPredefinedSARMenu_UI()

Most likely they need XtRemoveCallback() and XtFree() just like line 621 of list_gui.c

Look for XtFree through the code.

list_gui.c:390 should probably get the same treatment as list_gui.c:625. It is probably at least a memory leak but could also leave callbacks around that could be activated against long-closed Station List windows.

@we7u we7u added the bug label Apr 25, 2019
@we7u we7u self-assigned this Apr 25, 2019
@we7u we7u added the 4 Minor label Apr 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant