Program virtually freezes after 1st action

On several of my machines running under WinXP 32-bit Opus can be started and usually the 1st operation proceeds as expected, i.e., copy a file, move a file, etc. But then Opus sucks up 80-99% of the CPU and the largest chunk of memory. Then any action that is initiated takes forever to process and most of the time it never does. In task manager a typical set of numbers would be 59 processes, 100% CPU usage (Opus 85-99%), Opus memory usage 250,000, VM size 244,000, commit charge 999M/1895M. On the computer experiencing the greatest symptoms I installed a memory manager about a month ago (which helped with the low on page file size messages) but the problem with Opus started in the last couple of days. The problems I found in reading the FAQs are not quite the same as what I'm experiencing. Any thoughts on how to track this down and resolve the problem?



With constant high CPU usage, you might be able to find out what's causing it using Process Explorer:

[ul][li]Launch Process Explorer.[/li]
[li]Sort the process list by the CPU column (i.e. sort by CPU usage) and confirm that dopus.exe is actually the process using a lot of CPU.[/li]
[li]Right-click dopus.exe in its process list.[/li]
[li]Select Properties, then Threads, and sort the list of threads by the CPU column.[/li]
[li]Select the thread using all the CPU, then click the Stack button below the list.[/li][/ul]

You'll see a list of DLLs (followed by "!" and then some other information), with dopus.exe also somewhere in the list. There will usually be several Windows DLLs included the mix (e.g. USER32.dll, kernel32.dll, ntdll.dll) which can generally be ignored.

See which other DLLs are there, paying most attention to the ones nearer the top of the list.

Close and reopen the stack window a few times so that you look at a few snapshots of the stack, to make sure you are looking at a typical example and not an anomaly. (If a single component is using a lot of CPU then it will usually be shown in the snapshots, but it won't always be, so looking at several snapshots reduces the possibility that you take the snapshot at an unlucky time and miss the important details.)

If there are DLLs near the top of the list that aren't related to Opus then the CPU usage may be caused by a 3rd party component, often a shell extension or video codec. You may recognise it from the DLL name alone, but if not you can search your C:\ drive for that DLL name to see where it's coming from, and once found open the Properties dialog for the DLL to get more information.