Possible memory leak by requesting file attributes about dokan HOT 3 CLOSED

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!

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.

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.