I just hit this again on a different machine, several minutes after enabling `browser.tabs.firefox-view-next` on that machine and looking at the redesigned Firefox View. In today's case, Firefox Nightly unexpectedly hanged for ~tens of seconds, and then shortly later hanged for several minutes, and this repeated with short periods of everything being fine in between hangs. (I sort-of captured one of these several-minute-hangs in the profiler, but I ended up giving up and killing Firefox while the profiler was capturing the profile; filed bug 1849897 on that.) Could we either get this patch landed or just back out the original patch ASAP? We've invited folks to dogfood the `browser.tabs.firefox-view-next` about:config pref (internally via slack at least -- not sure how broadly), so there's potentially a population of users who are having a confusing/bad time due to this right now, potentially without them having any clue about what's going wrong or what to toggle to get back to a working state.
Bug 1849219 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I just hit this again on a different machine, several minutes after enabling `browser.tabs.firefox-view-next` on that machine and looking at the redesigned Firefox View. In today's case, Firefox Nightly unexpectedly hanged for ~tens of seconds, and then shortly later hanged for several minutes, and this repeated with short periods of everything being fine in between hangs. (I sort-of captured one of these several-minute-hangs in the profiler, but I ended up giving up and killing Firefox while the profiler was capturing the profile; filed bug 1849897 on that.) Could we either get this patch landed or just back out the original patch ASAP? We've invited folks to dogfood the `browser.tabs.firefox-view-next` about:config pref (internally via slack at least -- not sure how broadly beyond that), so there's potentially a population of users who are having a confusing/bad time due to this right now, potentially without them having any clue about what's going wrong or what to toggle to get back to a working state.
I just hit this again on a different machine, several minutes after enabling `browser.tabs.firefox-view-next` on that machine and looking at the redesigned Firefox View. In today's case, Firefox Nightly unexpectedly hanged for ~tens of seconds, and then shortly later hanged for several minutes, and this repeated with short periods of everything being fine in between long whole-browser hangs. (I sort-of captured one of these several-minute-hangs in the profiler, but I ended up giving up and killing Firefox while the profiler was capturing the profile; filed bug 1849897 on that.) Could we either get this patch landed or just back out the original patch ASAP? We've invited folks to dogfood the `browser.tabs.firefox-view-next` about:config pref (internally via slack at least -- not sure how broadly beyond that), so there's potentially a population of users who are having a confusing/bad time due to this right now, potentially without them having any clue about what's going wrong or what to toggle to get back to a working state.