Qtwebengineproc consumes almost all RAM after boot

After boot the system qtwebengineproc starts to load a lot of memory (up to 8 Gb) for first 5 minutes or so. Then memory usage gets normal.
It starts happened last week.
What is the reason and how to fix it?

Modedit: do not post useless screenshots (no additional information), save the server and the planet!

What is the full path to this process, since this is part of many packages?

Have you tried to trace which parent application launched the specific QtWebEngineProcess instance with your task manager?

Can you tell me how to do that?

The easiest way is likely:

pgrep -af qtwebengineproc

… followed by

pstree -aps <PID>

Note that htop will also show a “tree” view, when you hit F5, but you might not have that installed (yet; I recommend it). :wink:

Every gui task manager will also show you the process tree.
But lately i use the TUI bottom (btm). ? shows help, but generally you click on a section and hit E to expand it. T switches to tree view, you can sort with the mouse clicking on the column headers or hit F to freeze. Hitting DEL will offer to kill the process. CTRL+F opens the search.

There is, of course, one rather important thing I forgot to ask @pp2222 for; some System Info.

I’ve posted my mini-guide below for reference.

@pp2222 Please copy and paste the entire output from this Teminal command:

inxi -zv8

Note that the output produced by this command is privacy-filtered.

Please also remember to use proper code formatting as this makes it much easier to read on the Forum:

[Mini How-To] format code or command output

Select and copy all the text in the Terminal window (minus the prompt, if you are using zsh).
Then paste the output in between two lines containing three backticks
```
or three tildes
~~~

Or:
Copy & paste, then highlight the pasted text and click the </> button at the top of the reply window (easier for smaller outputs).

Cheers! :wink:

Your system information is a general prerequisite for every Support topic you create. This allows others a better idea of how to respond in the context of whatever Display Environment (DE) or Window Manager (WM) you happen to be using.

Please provide inxi output presented according to forum guidelines; see the Mini-HowTo’s (immediately below). :point_down:

Regards.


[Mini-HowTo] Provide System Information

Basic details provided by *-fetch type apps might give enough information for someone wishing to buy a computer, however, for Support purposes it’s best to ask your system directly.

Output of the inxi command will generate more useful and detailed information for those who may wish to help:


Suggested inxi command (use either):

inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)

Command output should be presented as pre-formatted text in accordance with forum guidelines. :eyes:


Running inxi within a chroot environment

  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0

Your privacy is respected


[Mini-HowTo] Present code or command output

Note: Grave accent (or, backtick) characters are used. :eyes:

For inline code or to show a single command:

  • please follow this simple example: code here.

For multi-line command output:

  • place text beween two rows of three (```) backtick characters to form a scrollable text box, or …
  • use the </> button in the Compose window to achieve the same result.

The empty row between these rows of backtick characters is where to paste any multi-line command output (such as inxi).

An example of a pre-formatted text enclosure:

What is a Quark?

A. In Physics, an elementary particle and fundamental constituent of matter. 
B. A character from the Star Trek: "Deep Space Nine" television series.
C. A soft, creamy, usually unsalted cheese traditional to central Europe.

Thanks everyone for trying to help me!
Since I posted here, I’ve only encountered this problem once, at which point I forced the process to stop using the ‘kill’ command. I also uninstalled the Deepl widget just in case, as I don’t use it anyway. And this issue hasn’t happened again for several days now!
I’m still keeping an eye on it and want to make sure it’s not Waydroid, as that was the last app I installed.
If I manage to reproduce this bug again, I’ll post detailed information about the system and try to take a screenshot of the process tree in ‘htop’.

Thank you once again for your time, and I’ll get back to you with the results over the next few days, even if the bug doesn’t occur again!

It would be preferable if you post the output of the commands I provided above. Screenshots are not “searchable” and just unnecessarily consume server space, for the most part. :wink: