I’ve noticed in the past week or so that after having a team create session in one of my projects open for a while causes lag in the explorer (e.g. selecting objects takes a long time, objects cant be double-clicked because the latency is so high that Studio thinks the second click is a rename and not a double-click) and also performing certain tasks in the script editor (such as alt+up/alt+down to move lines up or down being slow and difficult to use since feedback is delayed).
When there are no scripts in view, the lag stops, but as soon as a script is in view again it starts happening again. It doesn’t matter whether the scripts are docked in the studio interface or are free floating windows, it happens as long as its open.
I’m not sure what exactly is triggering this, in these team create sessions I am frequently using Play Solo so it could be that – or it could just be something that happens slowly over a long time, like a memory leak.
Memory usage seems to vary, when I first noted the issue today was around 1150 MB (right after Play Solo), then it dropped to 850 MB and at the time of the recorded video below was 900 MB. Memory on first joining the session in that place is around 700 MB, so it’s not a huge difference and probably isn’t the source of the problem.
I don’t know of a good repro for this except “use team create for a while and try Play Solo frequently while opening, closing and editing scripts”.
Here’s a video showing some of the latency: https://streamable.com/al6u2j (Unfortunately ShareX failed to align my cursor correctly, probably since I have Windows scaled up so I can read things on my 4K monitor lol, but you can still see roughly what’s happening for the important bits)
