Swapping Rigs overtime with the Animation Editor causes the Studio Dragger to slow down

[aaron_mccoy (PleaseDontBanAaron)]

When swapping between rigs when using the Roblox Animation Editor, there appears to be some sort of memory leak, as using the Studio Dragger causes massive drops in framerate that only get worse overtime. This issue does not go away until Studio gets restarted.

Related bugs:

Changing Rigs while the Animation Editor is open can fill the Properties Widget with invalid entries

When using the animation editor widget and toggling back and forth between different rigs, there seems to be a random occurrence where something that was selected will have its properties permanently displayed in the properties no matter what you select. These invalid properties don’t seem to affect anything, but it bloats up the properties widget until a restart of studio is done. This bug appears inconsistently, but frequently enough that attempting to do any form of animation in studio with …

Selecting other Rigs while Animating a Rig will cause them to be permanently highlighted

As the title suggets, studio selection highlight seems get stuck when selecting other rigs that are not the ones you are currently editing (presumably only models with humanoids/animation controllers as other objects are unaffected) Repro steps: Place multiple rigs Select the animation editor and pick a rig Select other rigs in the explorer Rigs will no longer appear unselected when you’ve stopped selecting them The only fix is to stop the animation editor altogether, re-select the rigs and …

Video of dragger causing loss of framerate:

Video of same interaction except that I restarted studio:

Here’s a case where I had Studio running for several hours, animating on and off:

[Parraing]

Hi there! Thanks for your reports.

Tickets have been opened for each of them and we’ll investigate as soon as possible.

Cheers!

[Parraing]

Hello! Our apologies for the delay.

We are having difficulties reproducing your issue. You seem to be moving a standard Part around, not a rig. Which means that the ACE should be deactivated at that point (asking you to click on its window to reactivate it).

Could you possibly attach the place you’ve used to record your videos and provide a comprehensive list of steps to reproduce the bug?

Thank you!

[aaron_mccoy (PleaseDontBanAaron)]

I’ve sent you a DM of the place since it has sensitive information and also added more context

[Parraing]

Hi there!

Unfortunately I have been unable to reproduce your issue.

I have loaded your place, I have started the ACE, played around with it, selecting multiple rigs, animating some parts, etc… Then I have left the ACE open for the entire night, playing an animation.

This morning, there was no drop in framerate, and the memory footprint of Studio was exactly the same.

There is a small chance that that specific issue has been fixed very recently. Also, I have fixes for the other issues you mentioned above (although they are not in the released build yet), and maybe everything was connected.

I suggest we wait for those fixes to be released. In the meantime, since it seems like closing the ACE solves your issue, I suggest you keep doing that from time to time as a workaround.

Cheers!