Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Reduce false positive performance monitor detection #1438

Merged
merged 1 commit into from
Jul 29, 2019
Merged

Conversation

bluemarvin
Copy link
Contributor

No description provided.

@bluemarvin bluemarvin added bug This issue is a software or functional defect task This issue is maintenance or an operational requirement labels Jul 20, 2019
@bluemarvin bluemarvin added this to the v1.4 milestone Jul 20, 2019
@bluemarvin bluemarvin self-assigned this Jul 20, 2019
@bluemarvin
Copy link
Contributor Author

Depends on MozillaReality/vrb#66

@bluemarvin bluemarvin force-pushed the go-jank branch 2 times, most recently from 74a2722 to 99fd2c2 Compare July 23, 2019 01:15
@bluemarvin
Copy link
Contributor Author

Now depends on MozillaReality/vrb#67

@MortimerGoro
Copy link
Contributor

I tried ShaderToy and it took a long time to detect the jank. It's that on purpose to avoid false positives?

@bluemarvin
Copy link
Contributor Author

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.

@MortimerGoro
Copy link
Contributor

MortimerGoro commented Jul 23, 2019

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

@bluemarvin
Copy link
Contributor Author

Okay, sounds broken 😓. I’ll take a look when back to my computer.

@keianhzo
Copy link
Contributor

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.

@keianhzo
Copy link
Contributor

@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.

@MortimerGoro
Copy link
Contributor

I get some crashes when trying Shadertoy:

2019-07-24 10:28:09.825 976-1334/? W/ActivityManager: Force removing ActivityRecord{b8a0723 u0 org.mozilla.vrbrowser.dev/org.mozilla.vrbrowser.VRBrowserActivity t13930}: app died, no saved state
2019-07-24 10:35:50.867 976-1087/? I/ActivityManager: Process org.mozilla.vrbrowser.dev (pid 3474) has died

Probably related to memory limit because I don't see a stacktrace.

@bluemarvin bluemarvin changed the title Fix false positive performance monitor detection on Go Reduce false positive performance monitor detection Jul 26, 2019
@bluemarvin bluemarvin merged commit 0298c68 into master Jul 29, 2019
@bluemarvin
Copy link
Contributor Author

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.

@bluemarvin bluemarvin deleted the go-jank branch August 1, 2019 17:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue is a software or functional defect task This issue is maintenance or an operational requirement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants