BindToClose 100% Infinite Yield

Bug Reports Studio Bugs
#21

Looking into it.

7 Likes
#22

“enable studio access to API services.”
What does that mean? How exactly do I do that?

4 Likes
#23

On a published game, on the website:

image

2 Likes
#24

Go into your game settings and enable the checkbox. Data stores don’t work in studio by default.

2 Likes
#25

Took me all day but I figured out what the problem is. Solution forthcoming (keep in mind normal delay for testing & rollout).

Thanks for the heads up.

15 Likes
Accurate Play Solo
#26

Thank you senpai :bow:

1 Like
#27

If you don’t mind me asking, what was the issue? Or is that sensitive info?

1 Like
#28

Not particularly sensitive, no.

In a nutshell there is a problem if we set up the “edit” data model’s rendering before we close down the old outgoing “Play” data model: something about setting up the rendering blocks any kind of async/delayed calls associated with BindToClose.

I had to get help from a more senior/more smarter-er engineer to figure it out.

13 Likes
#29

I love hearing the solutions on bug fixes, extremely interesting, hopefully we’ll hear more!

8 Likes
#30

I’m still getting this bug :confused:

1 Like
#31

This fix hasn’t been rolled out yet

2 Likes
#32

They’re working on it. Hopefully it’ll be out soon (no :tm: required)

2 Likes
#33

This is still an issue :frowning:

1 Like
#34

Any updates on the rollout of the fix? This is very painfully slowing down development for me.

6 Likes
#35

Well, if anything good comes of this - it lets me test how my data system handles abrupt server closes while player data is still being processed. :joy:

3 Likes
#36

Here’s a direct repro that doesn’t require anything special. Studio simply hangs up for the maximum timeout duration if any functions connected by BindToClose have a yield in them, probably because it never resumes the Lua thread.

game:BindToClose(function ()
	print("Doing some work")
	wait()
	print("Done?")
end)

cc @CycloneUprising @DreamingMind

3 Likes
#37

Thanks.
Sorry this has taken so long.
We do have a fix but there have been complications with it.
I believe we have them sorted out, and the fix should go live with our next release (355).
Very sorry for the inconvenience. I know the APS release has been unacceptably buggy: we are reviewing internal processes to make sure this kind of this doesn’t happen again.

12 Likes
#38

Do you have an estimated date for when 355 will be released, or is that unknown?

1 Like
#39

Isn’t a new Roblox update every Thursday?

1 Like
#40

:man_shrugging:

1 Like