-
Notifications
You must be signed in to change notification settings - Fork 218
Reduce false positive performance monitor detection #1438
Conversation
Depends on MozillaReality/vrb#66 |
74a2722
to
99fd2c2
Compare
Now depends on MozillaReality/vrb#67 |
I tried ShaderToy and it took a long time to detect the jank. It's that on purpose to avoid false positives? |
How did you test it? If you launch with the broken url it will take some time to detect. But I don’t consider that the typical use case. But I could have broken it. The way it should work is after the frame rate has stabilized junk should take about two seconds to detect. |
I launched with the default URL, typed shadertoy in the awesome bar and opened it from the Google search |
Okay, sounds broken 😓. I’ll take a look when back to my computer. |
I've made some tests on the Go and false positives detection has improved for regular pages but shadertoy takes too long time to be detected and sometimes it crashes the app. |
@bluemarvin See to work much better than before, less false positives and although it still takes a while to jump in for performance intensive sites like shadertoy, it doesn't feel as long as before. |
I get some crashes when trying Shadertoy:
Probably related to memory limit because I don't see a stacktrace. |
I landed this because the false positives on the Focus were getting really annoying. We can tune further with follow ups or just turn it off if we don't feel it is helping. |
No description provided.