New answers tagged


Yeah, chromium doesn't care much when you stop one of its threads. cpulimit is, in 2021, really not the kind of tool that you want to use, especially not with interactive software: it "throttles" processes (or unsuccessfully tries to, in your case) by stopping and resuming them via signals. Um. That's a terrible hack, and it leads to unreliability ...


I think it might be useful to focus on finding why it uses this much CPU, using the Taskmanager built-in to chromium to find which tab is using it, or a profiler like perf and flame graphs. But if you really want to slow down the browser you should consider the modern built-in solution cgroups, see for example:


You are on an ARM64 (aarch64) system, Google doesn't provide repository for this architecture so you can't install Chrome from it. The RPM package you downloaded manually is for x86_64, you can't install it on ARM64, the error clearly says it: Cannot add package google-chrome-stable_current_x86_64.rpm to transaction. Not a compatible architecture: x86_64 ...


First, pavucontrol is just an UI for Pulseaudio, pavucontrol doesn't set anything by itself. Second, Pulseaudio is normally configured to remember sources and sinks per application, and if you start an application a second time, it will use those sources and sinks, unless they are not available. The "default source" or "default sink" is ...


Probably this could work for you: ?


For what it's worth, if you don't want to change the cache setting permanently, you can also run chromium temporarily with a modified environment. For instance, using bash: CHROMIUM_FLAGS="--disk-cache-dir=/dev/null --disk-cache-size=1" chromium

Top 50 recent answers are included