I think its not normal that it takes Studio 30 seconds to unfreeze after I press Stop after getting an Error while testing my game.
Its always like that and it slow down debugging a LOT! I remember it wasnt like that couple of months ago.
Expected behavior
The Engine should kill the process and let me get back to work instead of making me wait 30 Seconds!
Does this continue to happen if you disable your usage of ProfileService?
yeah, why would it be related to that system?
You can see in the screenshot I posted that between the Release of the profile and the unfreeze, it took 30seconds
The screenshot you posted shows that the script running past the deadline is TimeOfDayService:25 - Have you looked into why that script is triggering the shutdown deadline?
All the scripts that trigger the shutdown deadline have a task.spawn with a while loop in it.
Why they are not Killed?
Here is the TimeOfDayService:25
They are killed - the shutdown deadline is 30s! You’ll have to find what scripts you are running that are binding to DataModel:BindToClose and are delaying DM shutdown until the timeout hits.
The only script bind to BindToClose in the entire game is ProfileService.
And it seems to be turned off if we are in studio.
Any way to know why its doing this?
At this point I’m pretty sure it’s not a studio issue - but the intended behavior of the system. I think this discussion better belongs in #help-and-feedback:scripting-support. I’ve taken the note of surfacing this better back to the team but I don’t believe it’s a studio bug.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
