Memory Leak in Participant Viewer #36
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If images are generated in the participant viewer widget and the window gets closed, the memory that was used for the images does not get freed. This can cause memory usage to skyrocket if the process is repeated multiple times.
Heavily mitigated the issue. RAM is now properly cleared when the window gets closed, but still accumulates for each image that is manually expanded while the viewer window is opened.
Fixed in 1.2.0