-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests are slow when browser is minized #228
Comments
That's a really good question. I'm not sure what the answer would be. Out of curiosity, is there a reason you can't use Alternatively, if it is the process priority manager, perhaps you could turn it off via prefs?
? It looks like Firefox does that for xpcshell tests: // The process priority manager only shifts priorities when it has at least
// one active tab. xpcshell tabs don't have any active tabs, which would mean
// all processes would run at low priority, which is not desirable, so we
// disable the process priority manager entirely here.
user_pref("dom.ipc.processPriorityManager.enabled", false); |
Well maybe I wanna see my tests and so I explicitly don''t want to use |
That sounds reasonable. If it works for you, could you let me know? Thanks! |
Well, I tried and it does not solve the issue.
Firefox Developer 101.0b9 As or Chrome I found settings around that. Testing with currently: customLaunchers: {
FirefoxDeveloperNoProcessPriorityMangaer: {
base: 'FirefoxDeveloper',
prefs: {
'dom.ipc.processPriorityManager.enabled': false,
'dom.suspend_inactive.enabled': false,
'gfx.webrender.enable-low-priority-pool': false,
'dom.min_background_timeout_value': 10000
}
}
}, |
How about setting |
Ah no Note the performance drain is immense: It's 1 test/s when minimized and when focused it is like 200 tests/s (calculated based on the run time it takes). customLaunchers: {
FirefoxDeveloperNoProcessPriorityMangaer: {
base: 'FirefoxDeveloper',
prefs: {
'dom.ipc.processPriorityManager.enabled': false,
'dom.suspend_inactive.enabled': false,
'gfx.webrender.enable-low-priority-pool': false,
'dom.min_background_timeout_value': 10000,
'widget.windows.window_occlusion_tracking.enabled': false,
'widget.pause-compositor-when-minimized': false
}
}
}, |
How about |
Already tried 🙂 |
When you use
Firefox
and the window is minimized or not active which is running the tests, they run very slow.Question
How can I prevent this, as obviously I want to run my tests, even if they run in the background. So I guess there is no reason in our use case here for such a behavior.
So how can I disable that?
Or can you generally disable it by default?
Reason
As far as I know the cause may be the "new" Process Priority Manager on Windows' Firefox versions that prioritized tasks the user works on. So minimized windows of course are not considered a priority.
I am not sure whether this also applies to FirefoxHeadless.
The text was updated successfully, but these errors were encountered: