Thread creation error

[rjmoses]

Error message:

"Thread creation error: Not enough storage is available to process this command"

when accessing c:\Windows\winsxs directory.

Using freeCommander 2007.10a under Windows Vista Premium Home edition; ALL windows updates applied.

Exiting/restarting freeCommander locks up that pane. Closing and restarting FC causes the same error upon restart.

I can correct the problem closing FC and editing freecommander.ini changing fit rom "Dir1=C:\Windows\winsxs" to some other directory.

The winsxs directory contains 19,914 files, 4,973 directoies. (I wonder if Microsoft gets a cut of disk drives sales?)

Thanks

Ralph Moses

[Marek]

I can reproduce the problem, if the option "Show directory size" is active.

[rjmoses]

Sorry. I didn't realize that I had folder size on when I created the problem. You are correct---the problen only occurs when alt-f9, folder size is on.

Thanks

Ralph Moses

[Marek]

I have fixed the problem in the beta 309.

[DrNo]

Not so fast!!!

I'm using Vista x64 SP1 and Windows explorer doesn't open my photograph folders anymore.

My folders are arranged with 4,000 images max to make it easy so I'm using FC... and what I notice is the remarkable speed at which files are shown and cached. Not even vista does that.

However, I keep getting the thread creation error. whenever I do a quick scan of the entire directory from top to botton & back and forth to see how fast the images can fill up using the vertical scroll.

Sometimes I get a memory error but I feel it's because I'm pushing FC too hard and it doesn't have the capcaity to handle that much info at once. The good thing is FC doesn't crash.

Perhaps you can remove these errors message boxes and put the error in a textbox or label. This will free us up from clicking the OK button every time.

You can create this scenario by creating and duplicating several images and giving them different names. I just use 100001.jpg to 104000.jpg. I use VS2005 to duplicate images (automation) into 1,000s of files.

The problem is NOT present when all images have been cached (all thumnails are visible) no matter how fast you scroll up and down.

If the thumbnail caching is the problem I would suggest adding several more threads to read thumbnails. Also, I could try out that 309 beta to see if it will handle it.

Thanks.