Possible memory leak by requesting file attributes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Mount a directory with a couple of files as a drive using mirror.exe
2. Open task manager and look for mirror.exe, leave the window visible so
that you can see the memory usage of the process
3. Open the mirrored drive in windows explorer, position on a file and
check the properties of it
4. You will see the mirror.exe memory usage is growing by about 1M.
Repeating step 3. will continue to increase the memory usage.  

What version of the product are you using? On what operating system?
dokan-0.3.7.1181, Windows XP sp2

Please provide any additional information below.
This behaviour can also be seen in Total Commander and Alpap Salamander,
where it has more serous impact on memory usage. These file managers are
dumping the memory usage by about 10 megs (with 500 files in the mirrored
directory) by just listing the mount point. I think this happens because
these programs request all the file attributes for generating a directory
listing, while explorer only requests this information on explicit user
action (properties dialog). I might be wrong though.

This can be reproduced with sshfs as well. 

Original issue reported on code.google.com by kiss.kol...@gmail.com on 21 Sep 2008 at 11:19

[GoogleCodeExporter]

I believe not only the mirror.exe suffers from memory leak problem:
Using dokan/mirror in VMWare (with 256MB memory dedicated to the guest)
with PostMark filesystem benchmark after a couple of iterations the whole system
runs out of memory and crashes: 
first the mirror process exits unexpectedly without leaving a single error 
message.
Afterwords the guest system start to respond to mouse and keyboard events very 
slowly
and finally the whole operating system crashes. This indicates, that the kernel
driver also should suffer from memory leak problem and brings the whole system
unstable after a lot of file operations issued.

The dokan and windows version was the same as Laszlo described.

What steps will reproduce the problem?
1) Map C: drive to M: with mirror.exe
2) Extract the postmark.tar.gz to c:\postmark
3) Enter M:\postmark
4) Start up the postmark test by:
   postmark stress

Thanks for looking into this problem!

Original comment by tibor.k...@gmail.com on 21 Sep 2008 at 11:39

Attachments:

• postmark.tar.gz

[GoogleCodeExporter]

I was thinking of using the Dokan library. This sounds like a serious issue. Is 
it
safe to say Dokan is not stable enough for prime time ? Sounds like compared to 
FUSE
for Linux there may be many more releases needed to flush out all the stability 
issues.

Original comment by coder...@gmail.com on 9 Dec 2008 at 1:43

[GoogleCodeExporter]

Hello,
I take it serially, especially for BSOD. Please give me feedback if you find 
any 
problem. The stability of Dokan library has gradually improved by many 
feedbacks.

I think this issue is fixed on 0.3.9. I run postmark test for the latest 
version, but 
I couldn't find the problem.

Thank you for your report.

Original comment by asa...@gmail.com on 9 Dec 2008 at 4:03

• Changed state: Fixed