-
Notifications
You must be signed in to change notification settings - Fork 68
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
Meshfill leaves extra display plots lying around #1770
Comments
@chaosphere2112 this might be somewhat kinda related to #1424 - in that plot functions are not cleaning up after themselves correctly..? |
@durack1 Similar, but different; these get cleaned up when calling |
danlipsa
added a commit
that referenced
this issue
Jul 8, 2016
This deletes some displays which reduces memory leaks.
danlipsa
added a commit
that referenced
this issue
Jul 8, 2016
This deletes some displays which reduces memory leaks.
danlipsa
added a commit
that referenced
this issue
Jul 25, 2016
This deletes some displays which reduces memory leaks.
doutriaux1
added a commit
that referenced
this issue
Jul 26, 2016
BUG #1770: Display meshfill template elements through renderTemplate.
migrated to vcs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you plot a meshfill, it generates a bunch of display plots that need to be cleaned up. The offending code is here; in the rest of the pipelines, rather than directly calling
template.plot
, we callcontext().render_template
, which does this cleanup for us (as well as plotting time/date stamps in the top right). I tried usingrender_template
instead oftemplate.plot
, but it horribly breaks things (You can see the dashboard results here). @doutriaux1 and I agree that this issue can wait till 2.6.The text was updated successfully, but these errors were encountered: