DivXConnected.exe uses 99% CPU (Server 1.5.0 Build 47)
We recently upgraded our server (AMD Athlon 64, Windows XP Home Edition SP2) to the latest version of Divx Connected (1.5.0 Build 47), but are finding that the DivXConnected.exe application jumps to 99% CPU at least once a day; we had the same problem with 1.4, but it's happening far more regularly with 1.5.
Once it hits 99%, the server either becomes unusable or the menu system (on the box itself) becomes so slow that it's effectively unusable, and the application has to be restarted.
DivXConnectedMonitor.exe and DivXConnectedScanner.exe appear to remain at 0% and ~5% CPU, respectively.
Does anyone know why DivXConnected.exe is jumping to 99%? Or why DivXConnectedScanner.exe is constantly munching 5% of the CPU? Also, what do DivXConnectedMonitor.exe and DivXConnectedScanner.exe actually do?
License Agreement
NO COMMERCIAL USE: This License Agreement grants our community members the right to use the Software downloaded from DivX Labs for personal use only in order to evaluate and provide feedback about it to DivX, Inc. Commercial use of the Software or of the work products resulting from its use is not permitted under the Terms of Use of DivX Labs.- To read the full Terms of Use please visit the Terms of Use page.
- To inquire about commercial licensing please email us


This post will explain how to do a process dump so that we can see what is going on during the 99% usage.
http://labs.divx.com/node/4913
Just to let you know that we re-installed DivX Connected 1.5 for the umteenth time shortly after my most recent post to this thread and haven't had the 99% problem since.
However, I still don't understand why DivXConnectedScanner.exe is constantly using between 2 and 12% CPU - is there any way to make it slightly less pro-active? It doesn't need to be scanning my library for changes all of the time, surely?
The server's running on an AMD Athlon 64 3400+ (single core).
It would make sense if the CPU usage was high when it was in use, but the problem I'm describing happens when the server is NOT in use, i.e. when noone's watching anything on a DivX Connected box.
I spotted this thread, but I've already tried uninstalling/re-installing several times.
The DivXConnectedMonitor.exe and DivXConnectedScanner.exe monitor your shared folders I think.
99% is a lot but what kind of processsor do you use?