Web browser tab freezing and high memory usage when running dynamic automation tools alongside Proxmox VE web GUI is almost always the browser, not the server. The Proxmox GUI is just a web app, and automation tools like Selenium or Puppeteer eat RAM and CPU. Here’s the diagnostic checklist that actually narrows it down.
Check the obvious first: browser resources
Open your browser’s task manager (Shift+Esc in Chrome/Edge, about:processes in Firefox). You’ll probably see the Proxmox tab using 1-2 GB and the automation tool’s tab or extension using even more. Dynamic automation tools run JavaScript constantly, trigger repaints, and leak memory over time. That’s your culprit.
Disable hardware acceleration
Hardware acceleration offloads rendering to the GPU, but Proxmox’s noVNC console and automation tool overlays can conflict. In Chrome/Edge go to Settings > System and turn off “Use hardware acceleration when available”. In Firefox it’s under Settings > General > Performance. Restart the browser. This fixes tab freezing for a lot of people.
Isolate the automation tool
Run your automation in a separate browser profile or a different browser entirely. Selenium and Puppeteer are notorious for memory leaks when left running. Use a headless mode if possible — it skips the GUI rendering entirely. If you must run headed, add the --disable-gpu flag to Chrome. That alone dropped my tab memory by 40%.
Check Proxmox’s noVNC console
The web GUI’s built-in console uses noVNC over websockets. If you have a VM console open while automation runs, the constant screen updates will freeze the tab. Close console tabs you’re not actively using. Or use a native VNC client instead — the X2Go beats RDP and VNC on Proxmox post covers that.
Limit browser process count
Chrome and Edge spawn a new process per tab and extension. With Proxmox GUI plus automation tooling, you can hit 20+ processes. In Chrome/Edge, enable “Memory Saver” in Settings > Performance. Firefox has a content process limit in about:config — set dom.ipc.processCount to 4. This won’t fix a leak, but it stops the browser from ballooning to 8 GB.
If it’s still freezing, check the Proxmox side
Rare, but a slow storage or network issue can make the GUI hang. Check pvestatd is running on the host: systemctl status pvestatd. If it’s dead, the GUI won’t update and the tab can appear frozen. Also look at journalctl -u pveproxy for errors. But 90% of the time it’s the browser, not Proxmox.
My take
Don’t run automation tools in the same browser profile as your Proxmox GUI. Use a separate browser, headless mode, and disable hardware acceleration. That solves the tab freezing and memory spikes. If you need uptime monitoring for Proxmox, check this post on website monitoring — but that’s a different rabbit hole.
