зеркало из https://github.com/mozilla/gecko-dev.git
098790a8eb
On Windows, the profiler changes the timer resolution when the sampling interval is less than 10ms. However this change affects all of Firefox, which can change other behaviors, sometimes causing confusion when refresh-rate issues magically disappear when the profiler is running. So now by default the profiler will not change the timer resolution. This should rarely affect the profiler's effective sampling rate, unless all threads in a process are in a waiting state, in which case there is nothing new to sample anyway! The front-end is investigating ways to make sampling gaps more obvious, see https://github.com/firefox-devtools/profiler/issues/2962 If some power users really need the added sampling precision in some profiling sessions, the timer resolution change may be requested before running Firefox, by setting the environment variable "PROFILER_ADJUST_TIMER_RESOLUTION" to any value. Differential Revision: https://phabricator.services.mozilla.com/D115451 |
||
|---|---|---|
| .. | ||
| core | ||
| lul | ||
| public | ||
| moz.build | ||