You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you checked with the master branch after the merge of #4456? I cannot reproduce any of those 2 issues anymore.
The last change that went into #4456 after your initial report makes sure that the figure is closed when removed from the DOM (I.e. not visible in the notebook) That takes care of issue one because there is no longer a hidden figure to plot into.
I tried opening several figures and closing them again and I see no sign of a memory leak. As expected the memory consumption goes up with more figures. It may not be immediately released when the figures are closed however explicitly doing a garbage collect seems to drop the memory consumption to the same level:
Activity
jenshnielsen commentedon Aug 17, 2015
I tagged this as proposed next point release since:
I don't think these issues are critical and they are as far as I know also present in 1.4.3 but if possible they would be nice to fix in 1.5.0
tritemio commentedon Aug 18, 2015
For the record issue #4457 may also be related (@jenshnielsen probably it is your second point).
jenshnielsen commentedon Aug 18, 2015
Have you checked with the master branch after the merge of #4456? I cannot reproduce any of those 2 issues anymore.
The last change that went into #4456 after your initial report makes sure that the figure is closed when removed from the DOM (I.e. not visible in the notebook) That takes care of issue one because there is no longer a hidden figure to plot into.
I tried opening several figures and closing them again and I see no sign of a memory leak. As expected the memory consumption goes up with more figures. It may not be immediately released when the figures are closed however explicitly doing a garbage collect seems to drop the memory consumption to the same level: