bibikurosawa / dokan

Automatically exported from code.google.com/p/dokan
0 stars 0 forks source link

DokanSSHFS.exe CPU usage 100% #63

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Enter to a directory with lots of files using DokanSSHFS.exe
2.
3.

What is the expected output? What do you see instead?

One of two things occurs:

1) Windows displays an error:

"Location is not available, N:\ is not accessible. The parameter is 
incorrect."

when trying to open the drive created by DokanSSHFS.exe 

or if actually opens the correspondig drive

2)CPU usage hits 100% and the program hangs. However, DokanSSHFS does not 
seem to leak memory. In addition, no packets are sent to network.

It seems to me as if there were some kind of infinite loop in the program.

What version of the product are you using? On what operating system?

dokan-sshfs-0.2.0.1226 2008/12/11, Windows Vista Business x86 32-bit.

Please provide any additional information below.

Original issue reported on code.google.com by juhamatt...@hut.fi on 7 Feb 2009 at 3:12

GoogleCodeExporter commented 9 years ago
I have the same situation.
CPU hit 100% after browsing some folders. and keep 100%.

Original comment by mrdu...@gmail.com on 20 Mar 2009 at 5:37

GoogleCodeExporter commented 9 years ago
Not sure about "lots of files" - that happens in more or less random fashion.
Also, there's only one process/thread using the CPU that way, as it overloads 
only
one CPU kernel (my CPU has two)

Original comment by breqwas....@gmail.com on 26 Mar 2009 at 2:13

GoogleCodeExporter commented 9 years ago
same for me
sometimes 100% cpu usage
sometimes I get "Location is not available, N:\ is not accessible. The 
parameter is 
incorrect."
after trying to access a lot of file like when I want to copy a directory..

Original comment by wad...@gmail.com on 16 Jul 2009 at 1:28

GoogleCodeExporter commented 9 years ago
same issue here, after accessing some files, DokanSSHFS.exe process randomly 
(and 
quite frequently) goes to 100% CPU (actually 50% on my dual core system), the 
mounted 
drive no longer accessible. 
I used ProcessExplorer to probe the thread eating 100% CPU and the call stack is

ntkrnlpa.exe+0x6e9ab
ntkrnlpa.exe!MmIsDriverVerifying+0xbb0
hal.dll+0x2ef2
dokan.dll+0x61a1
dokan.dll!DokanMain+0x51e
msvcrt.dll!endthreadex+0xa9
KERNEL32.dll!GetModuleFileNameA+0x1ba

I'm using Windows XP Pro, SP3

Original comment by wesley....@gmail.com on 18 Aug 2009 at 8:09

GoogleCodeExporter commented 9 years ago
Well, one correction here, even on dual core systems sometimes DokanSSHFS.exe 
can 
take up 100% CPU (meaning multiple threads are busy looping). I got another 
call 
stack snapshot here

THREAD 1(25% CPU) TID 1240
ntkrnlpa.exe!HalPrivateDispatchTable+0x36
ntkrnlpa.exe!RtlUpcaseUnicodeString+0xbe
dokan.dll+0x61a1
dokan.dll!DokanMain+0x51e
msvcrt.dll!endthreadex+0xa9
KERNEL32.dll!GetModuleFileNameA+0x1ba

THREAD 2(25% CPU) TID 4496
ntkrnlpa.exe!HalPrivateDispatchTable+0x36
ntkrnlpa.exe!RtlUpcaseUnicodeString+0xbe
ntkrnlpa.exe!ZwYieldExecution+0x4f3
ntkrnlpa.exe!MmIsDriverVerifying+0xbb0
hal.dll!HalClearSoftwareInterrupt+0x342
dokan.dll+0x61a1
dokan.dll!DokanMain+0x51e
msvcrt.dll!endthreadex+0xa9
KERNEL32.dll!GetModuleFileNameA+0x1ba

THREAD 3(50% CPU) TID 6128
ntkrnlpa.exe!NtBuildNumber+0x43
ntkrnlpa.exe!MmIsDriverVerifying+0xbb0
hal.dll!HalClearSoftwareInterrupt+0x342
dokan.dll+0x61a1
dokan.dll!DokanMain+0x51e
msvcrt.dll!endthreadex+0xa9
KERNEL32.dll!GetModuleFileNameA+0x1ba

Windows XP Pro SP3 32bit

Original comment by wesley....@gmail.com on 18 Aug 2009 at 8:33

GoogleCodeExporter commented 9 years ago
I got the same problem on a dual core running under Vista Home edition...

Original comment by guillemc...@gmail.com on 20 Oct 2009 at 1:00

GoogleCodeExporter commented 9 years ago
Same problem here, after opening some files in Komodo Edit. After working for 
about
20 minutes the activity will spike to 100%

Original comment by sker...@gmail.com on 30 Oct 2009 at 10:39

GoogleCodeExporter commented 9 years ago
After opening a file dialog, the Dokan process kicked CPU usage (both cores) to 
90%+
and brought my machine to a crawl. 

Original comment by theshowm...@gmail.com on 28 Jan 2010 at 9:33