Closed bjack205 closed 4 years ago
That's really interesting. I can't reproduce it on master--I'm seeing 0% idle CPU in Chrome on Ubuntu 18.04 with the visualizer open.
Can you tell me exactly what steps you took to trigger the problem? I would also be interested to see if you also see the problem on master
. You can do ]add MeshCat#master
.
@bjack205 are you still having this problem? I still haven't seen it locally, but I'm interested in understanding what's happening on your system.
I did some more diagnostics and it seems to be a problem with Chrome, not MeshCat. It started hogging an entire CPU (the system would pass the computation from thread-to-thread occasionally, based on what I saw in the Resource Monitor) as soon as I opened a MeshCat visualizer, and stopped as soon as I closed the tab. It worked fine with Blink and Firefox. I reset Chrome to default settings and it magically fixed it... not sure what the source of the problem was :man_shrugging:
I must have had some odd setting enabled. I did check if disabling hardware acceleration in Chrome fixed the problem, and it didn't.
I'm getting excessive CPU usage on MeshCat version 0.10. I'm running Julia v1.4.1 and had this problem on Ubuntu 18.06 and Ubuntu 20.04. Switching down to version 0.9 fixed the problem.
Computer Specs: OS: Ubuntu 20.04 LTS CPU: i9-9900 @ 3.10 GHz x 16 Graphics: Quadro P1000 Memory: 32 GB Model: Dell Precision 3431 Workstation
Based on my status monitor, it seems to be hogging an entire thread / CPU:
It runs like this all the time, even when I'm not doing anything with MeshCat or interacting with the visualizer.
Let me know if you need me to send any more diagnostics.