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

Fix memory leaks #5

Merged
merged 5 commits into from
Sep 2, 2019
Merged

Fix memory leaks #5

merged 5 commits into from
Sep 2, 2019

Conversation

nqrcqn
Copy link
Owner

@nqrcqn nqrcqn commented Sep 2, 2019

No description provided.

We do not want to create a new RecipeView every time we need to refresh
the recipes; this leads to leaking RecipeView objects, which have
subscribed event listeners.  This isn't the most elegant solution, but
it gets the job done.
Also add a method to clear the contents of the RefreshView between times
it is displayed.  Recreating the RefreshView every time is a small
memory leak.
Recreating the StashView every time we want to refresh the stash is a
memory leak, and makes Procurement lag while it rebuilds the stash.  As
an added bonus, now the last-selected stash tab remains selected when
revisiting the stash.
The onStashLoaded events were not being fired when loading character
inventories, so 1) there was no loading message for these "tabs" when
refreshing [used] tabs, and 2) the appropriate actions to take when
reloading tabs were not happening.
@nqrcqn nqrcqn merged commit 4e077ae into nqrcqn:test Sep 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants