We’ve recently begun encountering a bug in our game, where, on occasion, the fps drops to the single digits for about 30 seconds, causing very bad stutters. We haven’t been able to identify exactly what in-game behaviors trigger this, but the microprofiler shows that this is due to the Sound job consuming a large amount of CPU time:
We have found that this is always preceded by the AvatarCreationServiceJob:
Since we don’t use AvatarCreationService anywhere in our scripts directly, this seems to suggest it’s linked to when a player first joins the game, but this is just a hunch
We’ve encountered this bug on a number windows systems, high- and low-end, including mine. Here are my specs for reference:
CPU: Intel(R) Core™ Ultra 9 275HX
GPU: NVIDIA GeForce RTX 5080 Laptop GPU
1 Like
Hello There! I hope you’re doing well.
Thank you for taking the time to submit this issue and for reading our message.
To help us move forward, we’d appreciate your support with a few questions:
Don’t worry — we’ve got you covered!
You can find step-by-step instructions on how to generate and send the microprofiler [How to post a Bug Report - Bug Reports - Developer Forum | Roblox]. Following these steps will help us better understand the issue and work on a solution more efficiently.
Thank you again for your cooperation!
Hey @RemiHiddoGames – it looks like this AsyncTask occurs at the same time as Sound – does that happen in all of the microprofile captures that you’ve seen?
Hi there! Apologies for the delay, after doing some more testing we do indeed see that this AsyncTask occurs at (around) the same time, generally after a small delay. I’ve attached a zip of a dump which is representative of how the microprofiler looks when this occurs.
microprofile-20251122-193421.zip (1.2 MB)
Hope this sheds some more light on why this happens!
Hi @RemiHiddoGames, is there any chance you could upload a .rbxl file that reproduces the problem in a private message?
Hi @RemiHiddoGames , just wanted to follow up again to see if you could provide an .rbxl file that reproduces the problem.
Also, does this happen for any sound asset or just some particular asset ids?
Hey @RemiHiddoGames – we flipped a flag that should have fixed this. The AsyncTask is now truly decoupled from the audio engine. It may still take a while in the background, but shouldn’t affect the Sound job’s ability to make progress anymore. Could you confirm whether this has improved the situation on your end?
