Skip to content
This repository has been archived by the owner on Dec 6, 2020. It is now read-only.

Memory leaks #128

Open
Nielsbishere opened this issue Jun 24, 2019 · 1 comment
Open

Memory leaks #128

Nielsbishere opened this issue Jun 24, 2019 · 1 comment

Comments

@Nielsbishere
Copy link
Contributor

Describe the bug
There's a few minor memory leaks regarding Qt and general destructors.

To Reproduce
Checkout feature_fix_memleak_2 in WispRenderer.
Launch Maya; attach VS; take capture of allocations.
Load plugin; unload plugin; take capture of allocations.

Expected behavior
Should clean up; but leaks ~30 MB CPU.

Screenshots
System (please complete the following information):
N.A.

Additional context
This thread will include all findings of memory leaks.

@Nielsbishere
Copy link
Contributor Author

~RenderPipelineSelectCommand is not being called; other than that, I found that some Qt elements were allocated somehow; which may or may not be because of the plugin.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant