Find in all scripts crashing Studio

In my latest project, attempting to search through all scripts leads to Studio locking up instantly which leads to a crash. This is not the case for other, older, project files I have which do not suffer from this issue, even though they have substantially more scripts within them. Very rarely it searches instantly without issue, though even searching for the exact same text, less than a minute later, leads to a crash. But when search does work however, it will work for about half a minute or so, regardless of what you search.

I’ve tried copying as well as completely remaking the scripts in a new place file, with no success. The search will always freeze and crash Sudio after a certain number of scripts have been added, regardless of name. For example, all the scripts under ServerScriptService can be inserted into a new place file without crash and vice versa with the scripts under StarterPlayerScripts, but inserting both of them will lead to a crash. Even cloning the scripts multiple times under one of these 2 directories will lead to a crash.

Just searching the currently opened script works without issue. This issue has been replicated by other users with the same project file.

This is an extremely frustrating bug that I cannot pinpoint the exact circumstances under which it occurs, aside from that it occurs with the contents of my scripts after a certain number of scripts have been added. And that it can be replicated for other users besides myself under the same project file.

A published version of the place file can be found here, for any staff members investigating the issue. Just search for something like “print”.

4 Likes

I had an issue that caused the same thing earlier this year. Can you check to make sure it’s not the same root cause?

2 Likes

I’ve also experienced crashing with this recently. I can’t reproduce it very easily yet though

1 Like

Thank you for bringing that thread to my attention, as docking the search results fixes this issue, which I’ll be using for the time being.

It’s a different bug though that’s causing the crashing in my instance however as I cannot replicate the crashing experienced in that thread’s repro, which I’d also assume has been fixed by this point. Though it could be something similar given that docking the results fixes the issue.

This is still a really strange bug however, given that it only affects that one place.