We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Process manager - identify which window is hogging memory

  • 3 respuestas
  • 0 tienen este problema
  • 2 visitas
  • Última respuesta de ackerbilk

more options

The process manager tells me which window/process is hogging memory. But I have multiple windows open on multiple workspaces. How do I switch to that window so that I can see what it is and decide what to do about it?

Until recently, clicking on a window listed in the process manager would bring that window to the current workspace (ubuntu/xfce). That changed recently. Now clicking/double-clicking does nothing and there only seems to be the option to kill the process.

I guess I can kill it and then look at recently closed windows to see what it was. But that is a bodgy.

Can I fix the process manager so that when I click on one of its listed windows, I get taken to that window on the workspace where it resides? (It always was inconvenient when previously, double-clicking on the window in the list, brought that window to the current workspace. You had then to work out where it had come from if you wanted to put it back).

Firefox's window/workspace management is otherwise excellent. It's the best in my opinion. When it starts-up, for example, it puts all the windows back on the workspaces where they were when it was last closed. Very nice.

The process manager tells me which window/process is hogging memory. But I have multiple windows open on multiple workspaces. How do I switch to that window so that I can see what it is and decide what to do about it? Until recently, clicking on a window listed in the process manager would bring that window to the current workspace (ubuntu/xfce). That changed recently. Now clicking/double-clicking does nothing and there only seems to be the option to kill the process. I guess I can kill it and then look at recently closed windows to see what it was. But that is a bodgy. Can I fix the process manager so that when I click on one of its listed windows, I get taken to that window on the workspace where it resides? (It always was inconvenient when previously, double-clicking on the window in the list, brought that window to the current workspace. You had then to work out where it had come from if you wanted to put it back). Firefox's window/workspace management is otherwise excellent. It's the best in my opinion. When it starts-up, for example, it puts all the windows back on the workspaces where they were when it was last closed. Very nice.

Solución elegida

False alarm.

I see that the windows I can't double-click on in the process manager list are not windows but windows grouped by domain. They seem to be the process hogs, but they are collections.

So when I see "Firefox" window is using 50% CPU, it is not a Firefox window but all of Firefox, and that's why I can't switch to it.

Indeed, if I click on a window window, I do now actually get taken to it on the workspace where it resides.

All is well, and as much as I could have hoped for. Thank you.

Leer esta respuesta en su contexto 👍 0

Todas las respuestas (3)

more options

Solución elegida

False alarm.

I see that the windows I can't double-click on in the process manager list are not windows but windows grouped by domain. They seem to be the process hogs, but they are collections.

So when I see "Firefox" window is using 50% CPU, it is not a Firefox window but all of Firefox, and that's why I can't switch to it.

Indeed, if I click on a window window, I do now actually get taken to it on the workspace where it resides.

All is well, and as much as I could have hoped for. Thank you.

more options

Mark it as resolved and have a nice day. ;-)

more options

I see that the reason why I couldn't find any questions or help articles on this was because I was searching not for "task manager" but "process manager".