Yeah, that bug's fix should've addressed the issues discussed in comment 38 through comment 41, I think. I'd defer to reporter alex_mayorga on whether the performance is on-par with other browsers at this point. Though, given that we're up to 40+ comments and a handful of profiles and identified helper-bugs that have been spun off and fixed (on our end or on Google's end), I suspect it'd be most-manageable start fresh with a new bug for any remaining issues here, and consider this bug fixed-to-a-certain-extent-via-helper-bugs. alex_mayorga: would you mind retesting your Google Chat experience in Nightly when you get a chance, and see how we're looking comparable to other browsers? And if we're still noticeably not-as-good, could you file a new Core::Performance bug with a profile and link it from here? Thank you for all your help & profile-capturing here!
Bug 1698855 Comment 44 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yeah, that bug's fix should've addressed the issues discussed in comment 38 through comment 41, I think. I'd defer to reporter alex_mayorga on whether the performance is on-par with other browsers at this point. Though, given that we're up to 40+ comments and a handful of profiles and identified helper-bugs that have been spun off and fixed (on our end or on Google's end via site-redesigns etc.), I suspect it'd be most-manageable start fresh with a new bug for any remaining issues here, and consider this bug fixed-to-a-certain-extent-via-helper-bugs. alex_mayorga: would you mind retesting your Google Chat experience in Nightly when you get a chance, and see how we're looking comparable to other browsers? And if we're still noticeably not-as-good, could you file a new Core::Performance bug with a profile and link it from here? Thank you for all your help & profile-capturing here!