GP SoftwareTwitter
Opus FAQsManualCommandsObjects

Dopus.exe uses 25% CPU (solved: wav file problem)


#1

As soon as I start Dopus (double click on the desktop) dopus.exe starts using ~25 % of my CPU. Even if I don't do anything and only start it up.
Also, the blue circle for the "file and folder information" in the bottom left corner is constantly moving/spinning.
Only killing dopus.exe with the task manager removes the load.

I'm suspecting a relation to the Skydrive folder, but don't know.

I reinstalled Dopus, but the problem resurfaced shortly after.

Windows 7 64bit
Dopus Pro 10.2.0.0 (4645) x64

ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732 ntoskrnl.exe!KeWaitForMutexObject+0x19f ntoskrnl.exe!_misaligned_access+0xba4 ntoskrnl.exe!_misaligned_access+0x1821 ntoskrnl.exe!_misaligned_access+0x1a97 KERNELBASE.dll!GetProcessHeap+0x9 MFPlat.DLL!MFHeapAlloc+0x15 mf.dll!MFCreateUrlmonSchemePlugin+0x12c335 mf.dll!MFCreateUrlmonSchemePlugin+0x31840 mf.dll!MFCreateUrlmonSchemePlugin+0x31dae mf.dll!MFCreateUrlmonSchemePlugin+0x313f9 mf.dll!MFCreateUrlmonSchemePlugin+0x44552 mf.dll!MFCreateUrlmonSchemePlugin+0x44664 mf.dll!MFCreateUrlmonSchemePlugin+0x447a6 mf.dll!MFCreateSourceResolver+0x12bc3 SHELL32.dll!DriveType+0xf6b SHELL32.dll!Ordinal902+0x1872 SHELL32.dll!DriveType+0xe12 SHELL32.dll!Ordinal902+0x1985 SHELL32.dll!DriveType+0xccd SHELL32.dll!Ordinal241+0x21d0 SHELL32.dll!Ordinal241+0x1fad SHELL32.dll!SHGetFolderPathAndSubDirW+0x506 SHELL32.dll!Ordinal824+0x2a7d SHELL32.dll!SHChangeNotifyDeregister+0x48a dopus.exe+0x532658 dopus.exe+0x532eab dopus.exe+0x3624cc dopus.exe+0x536691 dopuslib.dll!IsWow64+0x31 dopuslib.dll!DummyDllFunctionToAvoidSymbolConfusion+0x60563 dopuslib.dll!DummyDllFunctionToAvoidSymbolConfusion+0x60617 kernel32.dll!BaseThreadInitThunk+0xd ntdll.dll!RtlUserThreadStart+0x21

ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732 ntoskrnl.exe!KeWaitForMutexObject+0x19f ntoskrnl.exe!_misaligned_access+0xba4 ntoskrnl.exe!_misaligned_access+0x1821 ntoskrnl.exe!_misaligned_access+0x1a97 KERNELBASE.dll!FlushFileBuffers+0x15d kernel32.dll!SetFilePointerEx+0x9 shlwapi.DLL!Ordinal166+0x524 mf.dll!MFCreateUrlmonSchemePlugin+0x445a8 mf.dll!MFCreateUrlmonSchemePlugin+0x44664 mf.dll!MFCreateUrlmonSchemePlugin+0x447a6 mf.dll!MFCreateSourceResolver+0x12bc3 SHELL32.dll!DriveType+0xf6b SHELL32.dll!Ordinal902+0x1872 SHELL32.dll!DriveType+0xe12 SHELL32.dll!Ordinal902+0x1985 SHELL32.dll!DriveType+0xccd SHELL32.dll!Ordinal241+0x21d0 SHELL32.dll!Ordinal241+0x1fad SHELL32.dll!SHGetFolderPathAndSubDirW+0x506 SHELL32.dll!Ordinal824+0x2a7d SHELL32.dll!SHChangeNotifyDeregister+0x48a dopus.exe+0x532658 dopus.exe+0x532eab dopus.exe+0x3624cc dopus.exe+0x536691 dopuslib.dll!IsWow64+0x31 dopuslib.dll!DummyDllFunctionToAvoidSymbolConfusion+0x60563 dopuslib.dll!DummyDllFunctionToAvoidSymbolConfusion+0x60617 kernel32.dll!BaseThreadInitThunk+0xd ntdll.dll!RtlUserThreadStart+0x21

ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732 ntoskrnl.exe!KeWaitForMutexObject+0x19f ntoskrnl.exe!_misaligned_access+0xba4 ntoskrnl.exe!_misaligned_access+0x1821 ntoskrnl.exe!_misaligned_access+0x1a97 ntdll.dll!RtlAllocateHeap+0xc5 MFPlat.DLL!MFCreateMemoryBuffer+0x11e MFPlat.DLL!MFCreateMemoryBuffer+0xb3 mf.dll!MFCreateUrlmonSchemePlugin+0x444a2 mf.dll!MFCreateUrlmonSchemePlugin+0x44664 mf.dll!MFCreateUrlmonSchemePlugin+0x447a6 mf.dll!MFCreateSourceResolver+0x12bc3 SHELL32.dll!DriveType+0xf6b SHELL32.dll!Ordinal902+0x1872 SHELL32.dll!DriveType+0xe12 SHELL32.dll!Ordinal902+0x1985 SHELL32.dll!DriveType+0xccd SHELL32.dll!Ordinal241+0x21d0 SHELL32.dll!Ordinal241+0x1fad SHELL32.dll!SHGetFolderPathAndSubDirW+0x506 SHELL32.dll!Ordinal824+0x2a7d SHELL32.dll!SHChangeNotifyDeregister+0x48a dopus.exe+0x532658 dopus.exe+0x532eab dopus.exe+0x3624cc dopus.exe+0x536691 dopuslib.dll!IsWow64+0x31 dopuslib.dll!DummyDllFunctionToAvoidSymbolConfusion+0x60563 dopuslib.dll!DummyDllFunctionToAvoidSymbolConfusion+0x60617 kernel32.dll!BaseThreadInitThunk+0xd ntdll.dll!RtlUserThreadStart+0x21


#2

Did you already check the steps in the FAQ?

[url]How to find components causing high CPU usage]


#3

Well the stuff I posted is from the stack of the dopus.exe. I'm not sure what most of the stuff means though.


#4

When you follow Leo´s instructions from the FAQ, you should see something like this:

As you see, the CPU usage can be seen on top of the list. That´s the place, where
you should look for the component, which is causing the high CPU.


#5

Okay thanks. I thought the stacks were what is necessary to (hopefully) solve the problem.

Here it is.


#6

The stacks are the important part (once the high-CPU thread(s) have been identified), so you were right the first time and Abr was just confusing matters. :slight_smile:

The three stacks in the root post all go through mf.dll, which is the Windows Media Foundation DLL. That, and the fact the file information thread isn't finishing, suggests the problem is triggered by a video file below the directory you are looking at, and may be a bug in a video codec/splitter which cannot process that file properly.

The Crash, exit or high CPU when viewing certain directories guide has suggestions which might help narrow things down.


#7

Yep, sorry. I was only concerned about the part, where the CPU load appears, because those dumps don´t tell us too much about CPU usage.
Nice new avatar, by the way. :smiley:


#8

Okay, I found the problem.
In one folder I had a wave file that could neither be opened nor deleted. The progress bar would just go on and on.
I managed to delete the file with Unlocker. It was quite the hassle to remove it from the recycle bin as well, but that's unrelated.

Everything is fine now.
The problem was on me, not Dopus.
Although I don't know what that was with the file. It was just a free song, downloaded from Soundcloud.
Anyway, thanks for the help.

PS: Dopus is best. :thumbsup:


#9

Glad it's solved.

If it happens again with another wav file, it'd be good for us to have a look at the file in case it's something we can prevent with a change to Opus. (It may be unrelated to Opus itself, and down to other components/codecs that are part of the mix, but it's worth investigating just in case.)


#10

Okay, but I don't think that's gonna happen. The file was seriously messed up, in Windows Explorer, too. Don't ask me why or how.