This has been happening to a few friends I know alongside players of my games. I have a microprofile log attached.
I’ve observed this happening in a few games:
https://www.roblox.com/games/4111023553/Deepwoken
https://www.roblox.com/games/9872472334/Evade
https://www.roblox.com/games/122421323102335/literally-just-an-empty-baseplate
System info:
microprofile-20250213-235315.html (6.9 MB)
I have been getting reports of this issue in our game Notoriety as well. Some users are reporting lag spikes when there’s many guns being fired, and after checking the Microprofile logs they have sent, it’s the same "SchedulerHostConfig.default” causing it.
It might be related to Sounds being created, since that’s what seems to be what takes most time of that CoreScript. I’m attaching the microprofile log we got in here as well:
microprofile-20250214-135921.html (9.8 MB)
From what I gathered, this has started today - before there were no reports about it beforehand.
I’ve been getting reports of FPS issues as well. I’ve attached screenshots of some of the reports I observed while investigating if other games had the same issue
https://www.roblox.com/games/4282985734/Fixes-Combat-Warriors
https://www.roblox.com/games/4588604953/Criminality
https://www.roblox.com/games/4111023553/Deepwoken
https://www.roblox.com/games/9391468976/HEIAN-Jujutsu-Shenanigans
The React scheduler has always been taking up huge frame times and causing huge lag spikes for me. I wonder if it’s severity only got worse to the point where it’s more noticable for everyone. I’ve reported about it earlier in different threads.
I am not so sure it’s a react thing. For some reason, it’s calling GetPropertyChangedSignal and indexing AncestryChanged a lot.
That’s interesting because as far as I know SchdulerHostConfig.default is the React Scheduler. That’s unless my information is wrong.
Eitherways, it would be cool if Roblox would document what these Corescript tags are all about.
Hey folks, the feature related to this has been rolled back as we investigate! You should no longer observe this behavior.
