After upgrading UiPath Studio to version 2022.10.1, it becomes unresponsive for about 10-30 seconds after making any change to my old projects. The old project main.xaml files are about 8MB in size and are Windows-Legacy.
- Environment details
Studio 2022.10.1 - 10/11/2022
License Provider: Orchestrator
Update Channel: Stable
Microsoft Windows 10 Pro 64-bit
16 thread 2.5 GHz to 4.9GHz CPU
- Activity package versions
- No errors
The projects are VB and they were fine on the previous version.
A change as little as adding another row to a Multiple Assign activity will hold a single cpu core at 100% for about 15 seconds.
I made a copy of one of the projects and halved the file size of main.xaml and it almost halved the slow down.
The attended bot’s functionality doesn’t seem to be affected. I haven’t heard any complaints from my users.
Is there a way to remove the graphical changes to the Studio UI? I don’t need the color-coded bars that I haven’t even seen any documentation to explain or menu buttons that do the same as a right click.
Afte upgrading my Studio to 2022.10.1 the same thing happened to me.
After making any simple change I have a delay of 30 seconds.
It is impossible to work this way. I hope that UiPath support will give us a solution as soon as possible!!
My main.xaml file also has 8.140 KB and Windows-Legacy dependencies.
Would you mind sharing a zip file of the affected project (before and after the conversion) with me via a private message?
Any updates on this as I’m having the same problem (slow Studio while editing projects) but under 22.10.3
I sent a project as requested, but I haven’t received any updates. My issue persists for 22.10.3. I had downgrade back to 22.4 to refactor all of my projects so that no single .xaml was larger than 2MB or so.
Thanks for the update @Steven_Raines1 and for sharing your solution.
If I get any info on that I’ll update here
Just to update. Studio 2022.10.4 should fix several performance issues.
Still extremely too slow with Studio 2022.10.5
Tried with .NET 6.0.13, but not change.
No development can be done…
More performance improvements are coming. We realize that this is a huge pain point right now.