How can I fix all of these infiniteyields?

[Hwk3r]

I’m getting all of these InfiniteYields in the output that don’t normally occur in any other game I make, so how can I fix this?

I’m not sure exactly when it started happening.

[eirav (yvo)]

Make sure that the assets you’re yielding to actually exist.
If your game uses StreamingEnabled, something like workspace.Part might not exist on the client, and so using :WaitForChild() will not work unless that part is rendered.

Infinite yield warnings occur when a :WaitForChild() call exceeds around 5 seconds. This happens either because the asset is not loading or it doesn’t exist. Make sure that the objects you are waiting for actually exist, as :WaitForChild() will continuously search for them until they are found. Additionally, it could be due to a bad internet connection, as those assets don’t always get to load within those 5 seconds.

You can add your own maximum wait time to a :WaitForChild() call, to do that you would have to do something like:

workspace:WaitForChild("Part", 0.5)

In this example, it will only wait 0.5s before giving you an error if “Part” doesn’t exist in workspace, unless of course it manages to find that part within that time range.

Make sure you search a little bit around the DevForum before posting, as there can be similar topics, such as this one:

Question: Does an infinite yield happen when the game can't find the instance's child?

Yes. If the humanoid isn’t found within 5 seconds, a warning will be printed, but the thread will continue waiting for the humanoid to be created. The block could be getting touched by an accessory’s handle, in which case hit.Parent would equal the accessory. For this reason, I normally use hit:FindFirstAncestorWhichIsA("Model"):FindFirstChild("Humanoid") instead. FYI, :WaitForChild also takes a second parameter: a maximum duration to wait for the child. If you set it to any number (e.g. 5) an…

[Hwk3r]

Thanks for taking the time to reply.

I’ve used the example code you’ve given me, and now they are gone.

[ProgrammerOnCoffee]

@eirav

In this example, it will only wait 0.5s before giving you an error if “Part” doesn’t exist in workspace, unless of course it manages to find that part within that time range.

Just a quick clarification for any future readers: :WaitForChild will not error if a child with the given name doesn’t exist, it will return nil.

That being said, the below code will error:

workspace:WaitForChild("Part", 0.5).Anchored = false

If “Part” doesn’t exist after 0.5 seconds, :WaitForChild will return nil, not error; however, attempting to get the Size of nil will error.