> For the complete documentation index, see [llms.txt](https://animoia.gitbook.io/animoia-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://animoia.gitbook.io/animoia-docs/guide/errors-and-recovery.md). # Errors and recovery ## GPU out of memory If the graphics driver resets, Animoia pauses, clears GPU resources, learns a lower cache ceiling, and rebuilds automatically. The dialog reports **Recovering** and then **Renderer recovered**. Your project isn't discarded. Lower **Preferences > Performance > GPU memory for frame caching** if it repeats. ## Unsupported or unavailable media An unavailable source renders nothing until it can be decoded or reimported. Some unsupported MOV codecs are demuxed to sequential frames automatically. Image-sequence failures and tracking reader errors are shown in their windows rather than replacing the project. ## Modal and playback locks Playback hides editing overlays and blocks document-changing shortcuts. Tracking, Footage Preview, Render, confirmation, close, and error windows own shortcuts while open. Crop mode blocks the rest of the editor until confirmed/cancelled. Saving remains available even while another modal is open. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://animoia.gitbook.io/animoia-docs/guide/errors-and-recovery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.