Skip to main content
Question

memory usage error

  • December 21, 2025
  • 1 reply
  • 4 views
oooeee

I have some kind of inappropriate memory error in my workspace - a crash in debug mode - "memory usage".
I have a workspace with three pages, and they've been working on it for a year - no errors.
I've done this, and there are a few photos left - the memory is 80% full.
I've tried to fix it many times, but the result is the same. I need to delete everything, and only then will the error stop appearing.
I did it through Help - troubleshooting - "reload all tabs" and "reset figma and restart". It didn't work. 
And I literally cleared the memory every time in debug mode - it went down to +- 30%, and it still gave me an error that it was 80+% full.

1 reply

TJ Kim
Figmate
  • TJ Kim
  • Figmate
  • December 22, 2025

Hi there,

Thanks for the detailed description — that definitely sounds frustrating, especially after the file has been stable for so long.

A few things to clarify: the “memory usage” value shown in debug mode can sometimes be misleading. Even if it drops after clearing memory, certain file structures can cause memory to spike again during rendering or interactions, which may explain why you’re still seeing 80%+ warnings.


Based on what you described, here are some troubleshooting steps that have helped in similar cases:
1. Check for large or complex assets
• High-resolution images, repeated bitmap fills, or large embedded photos are common culprits. Even a few remaining images can consume significant memory.
• If possible, try resizing images to their display size or replacing them with compressed versions.


2. Reduce complexity on each page
• Components with deep nesting, lots of boolean operations, heavy blur effects, or complex masks can add up over time.
• Try duplicating a single page into a new file to see if the error persists — this can help isolate whether one page or object is triggering the issue.


3. Look for hidden or unused content
• Hidden layers, off-canvas objects, and unused components or variants still count toward memory usage.
• Deleting unused pages, components, and styles can make a noticeable difference.


4. Break the file into smaller files
• For long-running workspaces, splitting pages into multiple files (for example, by feature or milestone) often improves stability and memory usage.


5. Test in a clean environment
• If you haven’t already, try opening the file in an incognito browser window or another browser to rule out extensions or cached state.
• If you’re using the desktop app, make sure it’s fully up to date.


If the issue still reproduces after trying the above, the best next step is to contact Figma Support and include:
• The file URL
• A short screen recording showing the memory warning
• Confirmation that it happens even after clearing memory and restarting

That’ll help the team investigate whether there’s a file-specific memory leak or rendering issue going on.
Hope this helps — let us know what you find after trying a few of these steps.

Terms & ConditionsCookie settingsAccessibility statement