How to prevent some tabs in Chromium from being killed?

[ceremcem]

I have my own web applications that I know they consume a lot of memory, especially during debugging. How can I prevent, for example, getting the tabs http://localhost:... killed last?

I guess the --avoid switch is not helpful here since it looks at the /proc/PID/comm content and all tabs contain the same "chromium" string:

$ ps -ef | grep chromium | awk '{print "/proc/" $2 "/comm"}' | xargs cat 
chromium
chromium
chromium
chromium
chromium
chromium
chromium
chromium
chromium
chromium
chromium
chromium
...

[CanNuhlar]

Basically, this is not possible. Cerem Cem ASLAN ***@***.***>, 20 Eki 2022 Per, 01:44 tarihinde şunu yazdı:

…

I have my own web applications that I know they consume a lot of memory, especially during debugging. How can I prevent, for example, getting the tabs http://localhost:... killed last? I guess the --avoid switch is not helpful here since it looks at the /proc/PID/comm content and all tabs contain the same "chromium" string: $ ps -ef | grep chromium | awk '{print "/proc/" $2 "/comm"}' | xargs cat chromium chromium chromium chromium chromium chromium chromium chromium chromium chromium chromium chromium ... — Reply to this email directly, view it on GitHub <#280>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPJ24RYIP25Y6SAF2OMIZTWEB2VZANCNFSM6AAAAAARJSJHNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[joeytwiddle]

FWIW I did read /proc/PID/cmdline in my exclusion_cmdline_regexp fork.

But my fork is very out of date with the official code. And the configuration is hard-coded in the source.