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!
Sorry you’re running into this issue. If you could DM me the link to the file (and share it with “firstname.lastname@example.org”) we can look into this for you.
Hey @raquino, we are also hitting this issue in some of our files. I had our designers write up a report on this and we have links etc along with repros, expected behavior and some suggestions for how to improve. Where can I send this document?
Hello! A similar problem with the file. We have already tried everything that was possible. Reduced the number of layers. There is still a problem. Compared with other files 3 times more, they have no such problem.
I am currently blocked by this File out of Memory error. I’ve just moved from Sketch+Abstract and like to keep organize my work in branches.
While I have come to love Figma, I am extremely disappointed in the performance issues around merging files. If you cannot handle enterprise grade files, read somewhat heavy files, then please do not GA the feature.
Still no answers to this?
We have also come across this issue and is a big show-stopper. Can you please help provide a quick fix?
Is there possibly another email address? When emailing to the email email@example.com, I got the following message:
We’re writing to let you know that the group you tried to contact (support-share) may not exist