Skip to main content
New Participant
November 6, 2019
Answered

[Crash/Load]-Massive performance problems (because of component use) with XD

  • November 6, 2019
  • 4 replies
  • 5785 views

Hello everyone,

Since I use the new components feature (I really love it!), the XD performance is going down with any new element I add or use in the design.
Now it has reached a point, where I can't do anything without crashing the whole programm. It even crashes, when I just want to save it offline.

 

Hardware:

I’m using a MacBook Pro 2018, 2,9 GHz 6-Core Intel Core i9, with 32 GB DDR4, and a Radeon Pro 560X 4GB graphic card.

That really should be enough for everything.

 

I’m working on a big app project with round about 150 screens that I have placed all on my canvas – together with my components collections.

 

At the moment I’m struggling with:

– File opening times of 2-5 min

– Auto save time (Cloud) of 1-5 min

– Crash of XD, now basically after any action

 

Working is unfortunately not possible that way!

 

The main problems (that all play together) are:

– Cloud auto-save, that makes working hell because of the long loading times

– Main components (e. g. the footer bar, header bar, accordions, that are on nearly any screen), including a lot of „inactive“ components, icons and setting, to be flexible in changing in the screens

– Repeat grid with large components are a direct XD crash, when I ungroup them

 

What makes it a little bit better (… but can't be the long term solution):

– Using a smaller window size for XD

– Working off-Cloud

– Using a separate file to group and build the screens and later paste them in the main layout (works until paste into the main file 😉 )

 

Is there anything else I can do be able to work again?

Thanks in advance for your help!

This topic has been closed for replies.
Correct answer HARSHIKA_VERMA

Hi Harshika, 

What's the status with this issue?

I have the same issues that is mentioned by the other users above.
Have your XD team come up with a solution on this yet? 

System: Windows 10

Thanks,
Kristophpher


Hi Kristopher and Marc,

 

I am sorry for the delay in response. I would like to confirm if your issue is resolved in the latest version of XD 31.2.

 

Please feel free to update the discussion and let me know if you need further assistance on the issue. I will try my best to help.

 

Thanks,

Harshika

4 replies

Pixels Digital Design
New Participant
June 15, 2023

I am having a similar issue on one of my projects about the cloud doc freezing and becoming unresponsive. The issue is using components with many layers and states. The reason for the many layers is the graphics we are using are svg vector graphics that have tiny parts/pieces at times. It's becoming almost unusable. So without flattening the svg graphics to a single image, what is the fix to this?

I don't remember having as many issues using vector graphics 4-5 months ago. 

dingoball
New Participant
March 9, 2021

I don't understand how this thread is marked as solved. The "Correct Answer" is not an answer at all, it's just a link to contact support. What's going on here?

Participating Frequently
March 16, 2023

I'm on version 56.1 and still experience this issue.  It's really really bad.  Components are great in theory but if we can't even manage them, there's no point in including them.  For the money Adobe gets for CC subscriptions, XD's performance is AWFUL!  

Participating Frequently
June 24, 2023

I'm still unclear what is happening between the two. I've yet to see anything evolve in XD from said partnership.  In the end, we might still be screwed if we choose to go Figma.  


Just this week I attended Config (Figma Conference).  It pretty rad and has some incredible features.  Belsky from Adobe was there to speak about AI.  Not a word was spoken about XD (or how awful it's been the last few years).  In light of the conference, I did find this article,   Adobe XD is on life support ahead of Figma acquisition - The Verge.

 

I'm not sure what this means for those of us currently paying at least a $55 monthly subscription fee for buggy software Adobe has clearly given up supporting, all before the acquisition of Figma is even final. After attending the Figma conference, we're moving forward with Figma implementation with hopes that once Adobe officially acquires it, they don't ruin it like they did XD.

Known Participant
December 4, 2019

Similar situation. Many layers for the same components and these components often inside other blocks of the interface.

Moreover, I have an issue with editing the names of the layers. Sometimes I simply cannot type anything and should relaunch the app.
For the record. Win 10. Adobe XD 24.4.22.1.

Maybe are there any recommendations for the number of artboards, components, elements, etc?

New Participant
December 4, 2019

Same for me here. Many components, sub-components, states and around 50 screens, and the performance is worst every day. Worst problem = Auto-Save as soon as i touch something. 

At the moment I’m struggling with:

– File opening times of 2-5 min

– Auto save time (Cloud) of +-5 min

- Always in saving mode

 

I'm lucky cause i didn't experience crashing yet.

Win 10. Adobe XD 24.4.22.1. No plugins used

New Participant
November 6, 2019

Hi All,

 

We are sorry to hear you are having trouble using components in Adobe XD. In order to investigate more about the issue, we would request you to please generate the log files using this link: https://helpx.adobe.com/in/creative-cloud/kb/cc-log-collector.html along with a sample XD file and upload it to a shared location such as Creative Cloud a. Once the files are generated, please share the url with me over a private message.

 

We will try our best to help.

 

Thanks,

Harshika


Can you please Adobe add a function to remove the autosave

 

 

November 26, 2019

Are you using a lot of images that are high res?

New Participant
November 26, 2019

No. Basicly I'm just using Vector files except some low res pictures.

November 26, 2019

Honestly not sure I know I have had a file with over 150 screens and it was working great. Do you have a ton of states within each component?