When joining any game on ROBLOX, I look in the console and see such warning from the debug library;
For reference the game I am playing in the photo is [BUFFS💸] Rags to Riches - Roblox however this bug also appeared in numerous other experience’s I have played.
To add to this, since it’s somewhat related, is debug.profilend just broken in the first place? Even when using the function just a few lines after a debug.profilebegin; I’m getting this warning in my own scripts. It only happens in certain cases, and honestly I’m not exactly sure on the criteria to get it to happen; but regardless, it is frustrating since there is a profile to close but the engine just doesn’t recognise it for some reason. However, perhaps this is just me not understanding the function correctly?
Thanks for the report! We’ll follow up when we have an update for you.
Just ran into the same warning. Program(s) that were made and running without errors before.
Just happen to check the log and found this … Unfortunately for your debugging, it doesn’t happen every time.
Thanks again for the report. This was disabled on November 11th after receiving a similar report.
For context, the microprofiler, debug.profileend(), will emit this warning if there isn’t a matching debug.profilebegin(id). This is only a warning message, not a crash, the calling script will continue to execute.
In this case, the warning was caused by an Asynchronous Roblox function call included within the measured window, blocking the main thread, not wrapped by a coroutine. If the Async function does not return within the same render frame, the microprofiler stack will be reset for the next frame, causing a mismatch when debug.profileend is eventually run, triggering the warning.
