BindToClose 100% Infinite Yield

[mjones_dewberry]

Mine is also hanging now when the Datastore request is in PlayerRemoving.

[Wingz_Avard (Avard)]

HttpService requests are yielding functions. As this bug happens when anything yields in BindToClose, calling Http Async functions within BindToClose when this issue is persistent will result in BindToClose yielding until it times out.

[DataBrain (Amber)]

The time it took to resolve this issue both times it happened is kind of concerning, given how many user reports there were and that it requires developers to manually work around it at the expense of potential data loss related bugs. Are there any test cases set up to prevent this from happening again?

[Automationeer (Eleanor)]

Hey @CycloneUprising, has the fix been pushed yet? I’m still receiving this error, and have to resort to using Test Server which is really slow and cumbersome for my work flow.

 15:26:08.427 - Not running script because past shutdown deadline (x117)

[AlgyLacey (Algy)]

Yeah, this issue is still happening for me too.

[Jaklic]

I think it’s been fixed. At least for me… I’m still waiting for the official patch info.

[nsgriff (griffted)]

This should be fixed. Please let us know if you have ongoing issues.

[acreol]

It’s not fixed for coroutines:

game:BindToClose(function()
	local t=coroutine.running()
	delay(1,function()
		coroutine.resume(t)
	end)
	coroutine.yield()
end)

There are many more coroutine bugs too:

ModuleScripts that yield with coroutine.yield() will break parent thread

If this is a server script: print'before' require(script.ModuleScript) print'after' and it has this ModuleScript as its child: local t=coroutine.running() delay(1,function() coroutine.resume(t) end) print'yielding' coroutine.yield() print'resumed' return nil Then the output will be before yielding resumed The ‘after’ is never printed, while it should be. If anyone happens to know a workaround, please let me know.

Coroutine.resume() bug while used in RemoteFunction & BindableFunction

I was excited to use the changed coroutine.yield on my project while I came across this coroutine issue while using it on RemoteFunction(OnServerInvoke). ServerScript: print("Server>> Initialized"); local remote = game.ReplicatedStorage.Request; remote.OnServerInvoke = function(player) local currentThread = coroutine.running(); print("Server>> Server invoked, Thread:",currentThread); coroutine.wrap(function() wait(1); coroutine.resume(currentThread, "Hello"); end)(); print("Server>…

Pcall/ypcall don't work with coroutine resume

This happens all the time in studio and in game print'-' pcall(function() local t=coroutine.running() delay(1,function() coroutine.resume(t) end) print'yielding' coroutine.yield() print'resumed' end) print'a'--never outputted, but should be Replacing pcall with ypcall doesn’t work either But the code runs with no problems if coroutines are replaced with wait() or BindableEvents I think this problem is similar to a lot of other ones with coroutines also

[CycloneUprising]

The fix I mentioned in earlier post is now live.

[Quenty]

Thank you so much!

Can you go over what caused it? Would love to know more!

[gillern]

This is still broken when using coroutines, the code below will error and freeze up studio

game:BindToClose(function()
	local thread = coroutine.running()
	
	delay(5, function()
		coroutine.resume(thread)	
	end)
	
	coroutine.yield()
end)

[LoveTheBears101]

I know this post is old but I would like to point out the bug still exists!


Basicly, the bug is whenever I try to use BindToClose() in studio, errors spam the output and I am unable to stop the game. I even tried closing studio, but when I re-opened the place it kept sending error messages. The error messages say:

09:56:46.706 - Not running script because past shutdown deadline (x115049)

and it never stops.
Here is a video:

It just keeps doing that infinitly.
Also, after I hit Stop, the game doesn’t fully close, it just keeps running and eventually freezes. I stopped it from freezing by using runService:IsStudio() to check wheter it’s in studio, and not use BindToClose() if it is, but when I hit Play it still spams the output (Because the errors never stop, so the errors are from when I first tested it with BindToClose())

If your wondering, I’m running Studio on a Macbook Pro, Version 10.15.4.

[Bausteinbuilder3]

Thanks for letting us know there’s still an issue here. If you can create a minimal rbxl file that repros this issue, it’s a lot more likely be able to fix it sooner.

[LoveTheBears101]

For some reason, it only does this on the game I’m working on, but here is a game that uses BindToClose in a script called Read-Me in the workspace:
Error.rbxl (17.8 KB)
You have to publish it to Roblox, otherwise it doesn’t do the datastores. It doesn’t spam the output like my other project, but it still freezes for a while.

[Dream5r]

The error has started occuring for me now also.

Whenever me or my friend plays the game and then press stop we get “Script that implemented this callback has been destroyed” and after pressing ‘OK’ on that prompt we get “Not running script because past shutdown deadline”

‘Show Details’ on “Script that implemented this callback has been destroyed” gives me my console output I would’ve gotten otherwise

Image of console output:

We’ve both tried restarting studio multiple times but nothing has worked. Its occurance rate like its happening in the video is like 80-90%.

[0therw0rldly (Fall)]

Soo…what’s the fix? I am using ds2 and this still occurs.

[Dream5r]

I don’t know about DS2 but my problem was that I accidentally moved my saving script to StarterGui.

[rutheniumm_ogg (Ruth)]

if you have admin in your game like adonis it causes the problem, it has bindtoclose inside the loader which causes this problem.

[buildthomas]

This post is marked as solved, please file a new bug report.