1365648 - Process hang monitor should specify which page is slowing down firefox

Status: NEW

(Core :: DOM: Content Processes, enhancement, P3)

Description

[William Lachance (:wlach)]

I occasionally get a message like this when using Firefox:

"A web page is slowing down your browser. What would you like to do?"

Before e10s multi, it was usually pretty obvious to me what was causing the problem, but now it's quite common for me to see this message when using another tab and the browser seems perfectly responsive, so it's pretty confusing/annoying to see this message. According to :ehsan, we have enough information to be able to be able to specify which page is causing the problem, so we should do that.

Comment 1

[(no longer active)]

Hi Markus,

Since you provided UX feedback on bug 1356334, and this info bar is basically the same thing for web pages, I thought you may be the right person to provide UX feedback on this as well.

The idea here is similar to that bug, we should be able to precisely tell the user which tab that they had open is causing the slow down and allow them to take action.

Would you mind recommending the appropriate kind of change to make here, if any?  Thanks a lot!

Comment 2

[Markus Jaritz [:markus] (UX)]

Was there an interaction designer working on creating those dialogs?
I'll forward my needinfo to :phlsa as he was interested in this as it impacts perceived performance.

Comment 3

[Kris Maglione [:kmag]]

Hm. I thought we showed the notification bar in the tab that was running the slow script, but apparently I was wrong.

It actually gets somewhat tricky to do that correctly, since multiple tabs can run in a single process, and a slow script in one tab can also slow down others... Ideally, we should show an infobar in all affected tabs, and in the tabs that are affected by the problem but not causing it, show a button to focus the problem tab.

(In reply to Markus Jaritz [:designakt] (UX) from comment #2)
> Was there an interaction designer working on creating those dialogs?
> I'll forward my needinfo to :phlsa as he was interested in this as it
> impacts perceived performance.

Yes, bug 1119442.

Comment 4

[Sylvestre Ledru [:Sylvestre]]

Clearing needinfo as Phlsa is no longer at Mozilla

Comment 5

[William Lachance (:wlach)]

Is there a way we can get this bug on someone's radar? It's still a pretty annoying issue.

Comment 6

[Markus Jaritz [:markus] (UX)]

(In reply to William Lachance (:wlach) (use needinfo!) from comment #5)

Is there a way we can get this bug on someone's radar? It's still a pretty annoying issue.

It's on my radar, and as soon as we get some time to focus on performance - hoping in the next months - we will look at this.