Bug 1849219 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.

I've noticed several times today that I'm getting multi-second parent process hangs.  I just captured this in the profiler and it seems to show us spending ~15 seconds in `mozilla::places::NotifyTitleObservers::Run`.

Nearly a third of that time is a garbage collection, but that seems like it may have been triggered by the JS garbage that the places task was generating, so I don't think it was just bad luck / bad timing.

Here's my profile: https://share.firefox.dev/45e57C3

I also did `kill -11` on my Firefox process earlier today when this was locking up my browser entirely (I wasn't able to start the profiler or regain control at all at that point).  Here's the crash report that that `kill` operation generated -- it's also in `mozilla::places::NotifyTitleObservers::Run()`:
bp-a4ff68d6-3b4e-417b-aa05-f71870230817

It feels suspicious that this is happening repeatedly today, when I haven't noticed it before. Seems like this might be a recent regression.  I don't have STR, unfortunately; I was looking at completely-different tabs/windows between the two times that I noticed the issue, and I noticed it just because my browser started locking up.
I've noticed several times today that I'm getting multi-second parent process hangs (which lock up the entire browser, and cause OS-level "application not responding, do you want to wait or force-quit" popups to appear).  I just captured one of these hangs in the profiler and it seems to show us spending ~15 seconds in `mozilla::places::NotifyTitleObservers::Run`.

Nearly a third of that time is a garbage collection, but that seems like it may have been triggered by the JS garbage that the places task was generating, so I don't think it was just bad luck / bad timing.

Here's my profile: https://share.firefox.dev/45e57C3

I also did `kill -11` on my Firefox process earlier today when this was locking up my browser entirely (I wasn't able to start the profiler or regain control at all at that point).  Here's the crash report that that `kill` operation generated -- it's also in `mozilla::places::NotifyTitleObservers::Run()`:
bp-a4ff68d6-3b4e-417b-aa05-f71870230817

It feels suspicious that this is happening repeatedly today, when I haven't noticed it before. Seems like this might be a recent regression.  I don't have STR, unfortunately; I was looking at completely-different tabs/windows between the two times that I noticed the issue, and I noticed it just because my browser started locking up.

Back to Bug 1849219 Comment 0