Slow open/save on 2025.2.6

we are running into a issue here with 2025.2.6

a project will run fine for a while but then maybe like once a day?

→ open or saving project A → super slow (Action: Saving Setup…) as in 5-10 minutes per save!

→ open random other project B → fast

→ open project A → fast again

after a while:
→ open or saving project A → super slow

.. rinse and repeat.

seems to be something we are encountering with 2025.2.6 only ? we where on 2025.2.3 before that and never observed it, i made a ticket but its almost impossible to reproduce “on the spot” case number: 25945455

just kinda writing it down in case other people have the same weird issue or someone knows a fix

linux project server, mac client for me

Hey Hi Finn,

I’m experiencing the exact same issue here!

To be honest, I initially thought it was a hardware bottleneck or a compatibility issue because my machine is quite old and a bit slow. But reading your post makes me realize it’s definitely a version-specific bug.

Up until a few days ago, I was running the 2024 version flawlessly with absolutely no issues. This sudden, frustrating increase in save and open times only started happening right after I upgraded to 2025.2.6.

Just like you described, it’s completely random and impossible to replicate on command, but it completely tanks the workflow when it hits. Thanks for opening a ticket and sharing the case number (25945455) I’ll be following this closely!

Thanks!

Is this specific to 2025.2.6 or also other versions of 2025.2.x?

As this was a service pack release that was released after all the other performance problems on 2026, it’s quite possible that some change slipped through that is the root cause.

In fact this may be a good thing. Until now these slow downs were mostly observed in 2026, which had a lot of changes, making it hard to pint down. If this service pack now leaked the problematic logic into 2025, it’s a much more contained amount of code. One just has to look at what files changed between 2025.2.5 and 2025.2.6 in the source control software, and now it’s a nice small amount of code to audit for a potential culprit.

we did not have this issue on 2025.2.3 thats the only thing i observed

does opening another project and then the original slow oen also fixes the issue for you temporarry?

To be honest, I haven’t noticed any difference or temporary fix by switching between projects.However, that might be because the projects I’m currently working on are quite light and not heavily loaded, so it’s a bit harder to judge the impact of swapping them. I’ll keep a close eye on it, and if anything changes or if I notice a pattern over time, I’ll definitely update everyone here. Thanks again for digging into this!

Could you install 2025.2.2? That’s the flavor I’ve been on for a while, and I haven’t seen these issues.

2025.2.5 is the GOAT… From what I see looking forward, we won’t be upgrading.

Might be un-related to your issue, but these are critical environment variables for us. No idea how to implement them on macOS, but we’ve done it studio wide on linux.

setenv DL_WELCOME_SCREEN 0  #No annoying Welcome screen

setenv DL_STARTUP_LIBS_CLOSED 1 #Don't try to load every Library upon Project opn

setenv DL_REMOTE_GATEWAY 0   #Hide MediaGateways.  Show local devices only.

Haha I was waiting for your comments expecting a good sign to jump to 2027.

We’ve now had to skip, 2026, 2026.1, 2026.2, 2027, with no end in sight.

Just made a client unhappy because we are sitting here watching actions to be saved.

10/10 stuff

update:

pretty sure its tlactions beign saved super slowely , espeiclly if they contain MKs

We need a thread for hidden away env vars

This one too… but make sure you know what you are doing with it.



setenv DL_ARCH_SKIP_TAR 1 #Disable Clip Lib backup

@finnjaeger could you update us on which version shows the issue? I am under the impression after discussing this issue with my Support colleagues that 2025.2.6 is not the cause of your issue.

we only saw it pop up on 2025 when we upgraded from 2025.2.3 to 2025.2.6

once a project gets “tainted” or whatever downgrading did not help .

So cant say, we never seen this before upgrading to 2.6 , but sure might just be a fluke/concidence that it happend right on the day after the update

Cool. Let me follow this up with our Support team.