'Not running script because past shutdown deadline' is not linking to a specific script in output log

Help and Feedback Scripting Support
1

Hiya, I recently got hired onto a fairly large game project, and ran into an issue.

Whoever made changes before me had a nasty habit of leaving loops that would keep running past game shutdown, leading the studio testing to be dreadfully slow.

image

I’ve gone through and fixed all the ones i can find, but now I just get this, a massive stack of 300+ of the same error with no script to link back to. I’m completely lost on their source.

Is there a possible way to trace back this error without checking the 50k lines of code that were made before I came on?

2

I’ve never seen this before. Maybe a Ctrl + Shift + F search for different loop types would help?

That being…

  • For i, v (or just looking for “For”) (also the in pairs)
  • While True/condition (or just search for “While”)
  • RunService (more difficult to search for maybe cause of Heartbeat and others, but search for those keywords)
  • something i might be forgetting

I hope that narrows down the scripts to look at. If anyone has other ideas, I’d also love to hear them. Sounds like a frustrating problem for sure.

1 Like
3

yeah,do this check for while loops.

when I get this error it’s usually because of a loop that is multiplying itsself or because of events being repidly fired when studio is closed. usually it’s loops or threads that are being created but sometimes it can be hard to find which script is causing the error.

4

I started getting these errors after a Studio update
Anyone else experiencing this?

5

Weird, it could be a code. Normally this error is thrown because when you try and stop running your game in studio (but the server is still active / frozen) it wont run the script because it’s past shutdown deadline and thats what kicks you out. Someone can correct me if there is other case scenarios but if you try to make a new baseplate and it seems fine then it most likely is your code (A.k.a for loops)

1 Like
6

Maybe check the Script Performance Tab in studio located under the view tab?
it would display all running scripts when playing/testing.
If not then also disable all scripts in your game and enable each one of them one by one after each play/testing, so one after time to locate the root cause.

1 Like