Running into "File out of memory" while resolving conflicts

Forum|Forum|5 years ago
July 9, 2021
45 replies
6452 views

Hi! As of lately I run into memory usage issue when trying to update branches from main.

The resource usage overlay shows a number around 0.3 G, which is well below the 60% of 2.0 G threshold, so working with the file didn’t trigger any memory warnings so far. But when working in a branch and trying to update from main, I recently started to run into warnings while going through the “resolve conflicts” dialog. It starts with the yellow warning banner, with every resolved conflict the shown memory usage % increases, the banner becomes red and ultimately I get to see the “File out of memory” message and can’t continue.

I wonder if this is just a temporary limitation/bug of the beta or if it would be advisable for the future to keep files well below the 0.3 G to use the branching feature.

Anyway, hope this helps, thank you!

Branching and merging

This topic has been closed for replies.

Best answer by djv

Hey All,

Solutions will be case by case, depending on your file. The forum is primarily managed by the community, so please reach out to the support team directly via this form for help: https://help.figma.com/hc/en-us/requests/new

Be sure to use provide a link to your file and share it with support-share@figma.com.

Show previous replies

Chris_Sullivan

I’m running into the same issue. Both the main file and branch are under the 60% safe file limit and I cannot accept updates from the main file in my branch without getting an error saying that the file has run out of memory.

Mike_Zharchev

Same here, branches are unusable for something bigger than a few frames.

tfabb

New Participant

Same issue here!

Mariella_Perez

Also experiencing the same issue. Is the only resolution to chat with support?

Carrie_Notte

I’m also having this issue and it’s extremely frustrating.

Both my Main and Branch are pretty clean in their builds and under 40mb combined. They were 112mb combined, but I took out some pages, hidden layers and cleaned up the components to reduce size and still have the issue.

Jayce_Yard

New Participant

Ran in to this issue today as well. Looking to fix this

Denise_Carofiglio

Same issue, please fix this. I based all files on branches and now they’re not usable.

Kate_Yz

Also experiencing this issue. We just switched to creating a branch for each of our concept rounds, to avoid heavy memory utilization when iterating in the same file. The memory bug in the branches is ironically worse than the original issue, despite the resource use reporting at .6G. This is also for enterprise design.

Van_Tran

New Member

Can we please get a response from Figma on what’s being done about this? Thanks