InvokeAI/invokeai
psychedelicious a6c91979af fix(ui): prevent canvas history leak
There were two ways the canvas history could grow too large (past the `MAX_HISTORY` setting):
- Sometimes, when pushing to history, we didn't `shift` an item out when we exceeded the max history size.
- If the max history size was exceeded by more than one item, we still only `shift`, which removes one item.

These issue could appear after an extended canvas session, resulting in a memory leak and recurring major GCs/browser performance issues.

To fix these issues, a helper function is added for both past and future layer states, which uses slicing to ensure history never grows too large.
2024-04-02 08:48:18 -04:00
..
app fix(config): handle windows paths in invokeai.yaml migration for legacy_conf_dir 2024-04-02 08:06:59 -04:00
assets feat(api): chore: pydantic & fastapi upgrade 2023-10-17 14:59:25 +11:00
backend feat(mm): use same pattern for vae converter as others 2024-04-01 12:34:49 +11:00
configs fix(mm): add missing v2-midas-inference.yaml 2024-03-27 07:48:54 -04:00
frontend fix(ui): prevent canvas history leak 2024-04-02 08:48:18 -04:00
invocation_api feat(nodes): "ModelField" -> "ModelIdentifierField", add hash/name/base/type 2024-03-10 11:03:38 +11:00
version chore: v4.0.0 2024-04-02 09:10:53 +11:00
__init__.py Various fixes 2023-01-30 18:42:17 -05:00