Skip to content

Objects not destroyed at the end of each round #23

Description

@gitchly

Not explicitly destroying/clearing objects after each round may lead to too much memory usage. The same goes for undo/redo, when a user has a redo queue but draws, the redo queue is not correctly destroyed.

This is especially apparent in the shader-renderer branch, where ShaderPath objects store multiple buffers and other values that may not get cleaned up correctly.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions