python3 maxing out CPUs when WebUI Open.

[UberPlexCa]

Describe the bug
Brand new install of Version | v5.1.1-20220603 main on Ubuntu Server 22.04.1
When you open the WebUI Python3 maxes out all CPUs on the thin client I use for alerts. The moment you close the browser CPUs go back to normal. I believe others have seen this issue as well.
The browser is Chrome.

Any tweaks that can be made to fix this? The thin client is a perfect box for the alerts it has no moving parts but it is CPU limited.

WebUI Open:

WebUI Closed:

Logs show this each time you open the WebUI

BrokenPipeError: [Errno 32] Broken pipe

Exception occurred during processing of request from ('192.168.1.20', 24843)
Traceback (most recent call last):
File "/usr/lib/python3.10/socketserver.py", line 683, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.10/socketserver.py", line 360, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.10/socketserver.py", line 747, in init
self.handle()
File "/usr/lib/python3.10/http/server.py", line 425, in handle
self.handle_one_request()
File "/usr/lib/python3.10/http/server.py", line 413, in handle_one_request
method()
File "/root/obplayer/obplayer/httpadmin/httpserver.py", line 262, in do_POST
self.send_content(response.status, response.mimetype, response.content, headers=response.headers)
File "/root/obplayer/obplayer/httpadmin/httpserver.py", line 178, in send_content
self.wfile.write(content)
File "/usr/lib/python3.10/socketserver.py", line 826, in write
self._sock.sendall(b)
BrokenPipeError: [Errno 32] Broken pipe

[UberPlexCa]

Any update to this?

[radiorob]

I have also encountered this, especially trying to host multiple players on one VPS. It is to do with the dated legacy architecture of the way it displays http interface when it was created at the time many years ago. @vincentthedev has started updating support for bootstrap themes that can be seen at the demo site on the Beta Player from the code on the testing branch. Generally speaking http access for the player is only for initial setup and config. After that the player box is command and controlled and managed by an observer.