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.
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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