I’ve been dealing with fleeting microprofiler hallucinations for a while now, from profiling scopes completely disappearing to inaccurate frame times, but I think I’ve hit such a critical bug that I just had to report it.
The “Timer” field in the microprofiler, which also happens to be the field that controls what is visibly displayed on a scope bar, is completely broken. It almost always shows the wrong information. To see the actual correct name of the scope in question, you must hover over a bar and look at the “Label” field.
In this particularly horrifying example, I have a “Timer” field showing a label from a completely different experience! I don’t even have this place open in Studio anymore, but I did 10 minutes ago. The fact that this is able to happen is extremely concerning. “Label” field here is correct.
I appreciate the new features Roblox engineers are adding to the microprofiler, but its stability and accuracy needs to be investigated and tested. This is a critical tool developers use for debugging and performance testing, and I’m confident that there’s something seriously wrong with how its tied into script labels.
Hello, and thank you for the bug report! This is because the Microprofiler is engine-wide and not aware of particular DataModel scopes, so to it there is no clear boundary between loading different experiences. As a work-around, I suggest restarting Studio between working on different projects to effectively “reset” the Microprofiler’s internal state.
We have filed a bug internally about this and will brainstorm a long-term solution, but we expect this to be a significant/large effort – not a quick fix. We will keep you updated.
Aside from the scopes leaking across places, it simply appears that the “Timer” field is almost always wrong, and the “Label” field is almost always correct. I’m hoping that the fix for this can come sooner, because the only real solution to using the Microprofiler in my experience is to hover over each scope to look at the “Label” field, since the text on the scope bar is associated with the “Timer” field and is wrong.
