When gathering the profile chunks from processes, there's a timeout to avoid infinite waiting. The default (and minimym) is 1 second as written in [1] but it can also be changed by a pref in [2]. https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/modules/libpref/init/all.js#650 We got several reports of losing subprocesses data, especially the ones that were interesting. There's the added issue that the speed will depend on the speed of the computer. Therefore I'd suggest to increase the timeout to 15 seconds. This is still small enough that if there's a real issue the user won't wait too long, but large enough to let the subprocess generate the json. [1] https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/tools/profiler/gecko/nsProfiler.cpp#1280-1283 [2] https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/modules/libpref/init/all.js#650
Bug 1958201 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When gathering the profile chunks from processes, there's a timeout to avoid infinite waiting. The default (and minimum) is 1 second as written in [1] but it can also be changed by a pref in [2]. https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/modules/libpref/init/all.js#650 We got several reports of losing subprocesses data, especially the ones that were interesting. There's the added issue that the speed will depend on the speed of the computer. Therefore I'd suggest to increase the timeout to 15 seconds. This is still small enough that if there's a real issue the user won't wait too long, but large enough to let the subprocess generate the json. [1] https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/tools/profiler/gecko/nsProfiler.cpp#1280-1283 [2] https://searchfox.org/mozilla-central/rev/7014a821bb4689deb04f647a153a6db10e580a00/modules/libpref/init/all.js#650