✅ Task Manager

Check on Wavebox's performance using the built-in Task Manager. It gives a real-time overview of processes running in Wavebox, plus CPU and memory information.

Open the Task Manager

• Click the Burger Menu (in the top-right of any window) > More Tools > Task Manager.
• Or, from the Navigator window, click on the chart arrow top-right to launch the Task Manager.
• ⚡️ Note that CPU usage normally increases when the Wavebox Task Manager is running.

macOS and Windows

If you open the macOS Activity Monitor, or Windows Task Manager whilst Wavebox is running, you may see several Wavebox-related processes each with their own resource allocation.

Wavebox, like many other browsers, splits its runtime into multiple processes, meaning each tab runs as its own process. This has advantages like as providing hardened security between tabs and improved stability.

• The macOS Activity Monitor shows several different names for Wavebox and these can be split into a few categories...
  • Wavebox - this is the main Wavebox process that manages the user interface and the other processes
  • Wavebox Helper (Renderer) - Each tab runs in its own process and these are listed as the render processes in the task manager
  • Wavebox Helper (GPU) - This process provides dedicated graphics processing and hardware acceleration to Wavebox
  • Wavebox Helper - These helper processes provide additional support for things like networking
• The Windows Task Manager only shows multiple Wavebox processes and doesn't give any additional information.

Wavebox Task Manager

Wavebox's Task Manager shows enhanced information about what each process is used for - this can be useful for debugging if one process has high resource usage, or if you're just curious. Some processes are specifically for tabs or extensions. Others provide general utility functionality such as network or audio services.

• You can correlate Wavebox processes with macOS or Windows
• See the "Process ID" listed in Wavebox and match it to the "PID" in the macOS activity monitor or Windows Task Manager.

Enable More In-depth Information

To see more information about Wavebox processes, open the Wavebox Task Manager and right-click in the table header. Here you can add additional columns that show more information about each running process.

Debugging High CPU, Memory Usage

To make sites work, Wavebox runs JavaScript code that websites include within them which sometimes uses a lot of CPU or memory, which can be detrimental to performance.

• If you see Wavebox running slowly or notice a process with high CPU usage, you can use the Wavebox Task Manager to investigate what is causing this.
• Open the Wavebox Task Manager
• Look for a process with an unusually high memory footprint, or high CPU load. (In the screenshot above, Facebook is using 194.9% CPU, which is unusual).
• Click the [End process] button.

Background on Processes

Wavebox creates multiple processes to speed up browsing, make your browser more resistant to crashes, and isolate tabs from each other, increasing security, performance and reliability.

Websites are complicated, and the more complex a website is, the more ways things can go wrong. If something does go wrong, it can result in a crash and if everything is running in a single process a single crash on one page can crash all of Wavebox. Isolating each tab in its own process means that a crash from one tab means just that tab will crash and not the whole browser.

The majority of computers these days have multiple processing cores, which means that they're great at multitasking. By splitting large portions of Wavebox into different processes, Wavebox can take advantage of this by splitting the workload more evenly across all processing cores on your machine. This results in much faster performance.

Running everything in separate processes also makes it easier to protect your computer against malicious code running on a website. Each process in Wavebox is sandboxed, which means they're mostly isolated from the rest of the system and only have a reduced set of privileges. If any malicious website tries to exploit Wavebox, the amount of damage it can do is limited to its own process and not the rest of Wavebox or your operating system.