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:
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
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.
Hi, would you be able to provide the microprofile file that you are taking screenshots from? The original issue was identified and rolled back; no additional changes since that time. It could be that the FPS issue for you has a different root cause, so having the microprofiler would be helpful for our own debugging.
Edit:
I believe I have mistaken Heartbeat;ugc for Heartbeat::LuaApp.
Regardless I believe this is a low hanging fruit for your team to resolve.
To add to the original thread’s topic…
I recall having major frametime spikes on the 22nd March 2025. It may be that this bug has been resolved as I have not been experiencing spikes of this nature via Heartbeat;ugc since then.
Hi folks, we’ve root caused the initial cause of this bug report to the Music window (opened via the topbar dropdown → Music menu). A fix has been rolled out to all platforms, so keeping the Music window open should no longer have any performance implications.
That said, as noted by others in the thread there are parts of the app flow that experience a similar issue attributed to SchedulerHostConfig.default. If you could file separate bug reports for those flows so we can disambiguate them and get them to the teams that will be able to address these surfaces it would be a big help!
I’m going to close out this report, but please feel free to reopen if any further issues arise from the Music window.
I have filed a bug report about the performance issues of the avatar editor on Mobile long ago and there was another one that includes the Mobile and UWP apps (Universal app) here:-
None of the above reports include any information about SchedulerHostConfig.default spiking, but nonetheless the causes of these lag spikes is of course that script as can be seen through the Microprofiler. None of the above reports got any staff response unfortunately.
Are these two bug reports sufficient or do we need to file another one that specifically includes the issue of SchedulerHostConfig.default spiking causing lag spikes?
Edit:-
I already filed a bug report that is broader about the topic of the issue. Essentially, after further testing, it actually appeared that every interaction with the Universal app results in the Corescript spiking, and it’s visible in the entire app excluding website based elements, and not just the avatar editor. The bug report in question:-
the performance of the avatar editor is not exclusive to any apps, its also been notoriously sluggish on the website for as long as I can remember, including long before UGC / high-poly models were common. It is way too performance intensive especially when many accessories have been changed within the window session (presumably a memory leak).
What you said is true and I agree with it. Though, I think that the causes of the performance issues in the avatar editor on the website differs from that of the Universal app.
Let me explain this further, what I can see causing the spikes through the Microprofiler in the avatar editor on the Universal app is Script_SchedulerHostConfig.default, the same script also does spike when doing anything else in the Universal app.