Studio closed the active project... critical internal error

Has anyone come across this with Studio? I am on version 2024.10.1 running on a MacBook Pro using Parallels. This has never happened before up until this version. I updated maybe a couple months ago, and this error happens non stop. It happens randomly. It’s driving me nuts! I have to reboot Windows every time this happens. I usually lose a lot of work, too.

image

@Josh_James

Can you open the details and show the full error here

Also does it work for new projects or is it happening for all?

Cheers

Hello @Anil_G - Below is the full error message. It happens for any project I open at completely random times.

24.10.1+Branch.master.Sha.9c270cffe65425641403b7809635c506d263462d.9c270cffe65425641403b7809635c506d263462d

Studio closed the active project due to a critical internal error. You may retry to open the project.

Error: UiPath.Studio.Contracts.RecoverableException: Studio closed the active project due to a critical internal error. You may retry to open the project.
at UiPath.Studio.Project.Client.Ipc.Services.ProcessTerminatedBehavior.HandleProcessTerminatedInternal()
at UiPath.Studio.Plugin.Workflow.Services.ProjectProcessController.b__20_0()
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler), HResult -2146233088

Hi @Anil_G - Curious if you were able to find anything about this error? This happens at least twice a day. Worked fine for years up until the 2024 versions of Studio. I don’t remember exactly when it started, but I know it happens on 2024.10.6 and 2024.10.1. I never used 10.5. Thanks

Does it happen on all projects or just certain ones?

Sometimes some newer features such as coded workflows can create scenarios where this happens, but it should not be happening routinely every day on different projects.

Happens every day, multiple times a day, on any different project ever since a few Studio updates ago.

@Josh_James

based on the hresult value…it is more a change in xaml or json would have triggered this error…can be random as well due to parsing issue or so…

to validate just take a back up of project.json and try to remove and reopen so that it gets created…if that is not the case then may be due to major changes in activities the xaml files might have some extra characters which might be effecting…

cheers

1 Like

I’ll give that a shot, thank you!

1 Like

I agree that this is super strange, can I check are you using Onedrive or something like that?

If you are storing these projects in a Onedrive location I can see it easily going wrong and this error happening.

I have not been encountering this issue in myself so feel like there is a third factor at play here rather than Studio being the core issue.

No. I’ve been opening my .xaml files from a local drive. I should also mention, this is also happening to the two other developers on our team. All 3 of us use Parallels. Maybe it’s Parallels? It’s worked fine for years using Parallels though… Not sure.

I think its usually advised to keep all the code locally rather than relying on shared drives and especially Onedrive because of sync issues but I believe a regular network drive should be more stable, I’d still avoid it though.

It is possible that something is going wrong on the syncing between your shared drives etc.

Could you experiment with working with the project on your C drive and see if it persists? If not then thats your issue.
I doubt its related to parallel activities. Those are just some regular activities and have been around for years and years.

I am opening from C drive. Parallels is a virtual Windows machine used for Mac, since Studio does not run natively on Mac. But, like I said, it has worked fine using Parallels for years up until now.

On damn, sorry. I misread about the local vs shared drive. My bad.

Hmm, I have never heard of that Parellels thing for Mac so I don’t know if that could cause it.

No worries. Yeah, Parallels is great. It’s nice being able to use Studio on a Macbook Pro. The crashing isn’t to the point where I can’t use Studio anymore, it’s just super annoying when it happens. The downside of using it when things like this happen are that there are tons of variables as to why it crashes… Could be Studio, could be Parallels, could be the MacOS version… Who knows… Just super odd that it happened to all 3 of us on the team at the same exact time.

I have not had a crash in over a week, which is a new record. Almost two weeks, actually. I believe the latest version of Parallels (Version 20.1.2 (55742)) fixed my issue. That is the only thing different.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.