Custom Query (8170 matches)

Using FileZilla server v0.8.5, windows 2000.

I just replaced Cerberus FTP server with FileZilla, so I already had a bunch of directories set up for FTP, full of stuff.

While adding users, I was assigning home directories. When the directory explorer window opened, I began expanding to get to the D drive.

My D drive has several directories, each with nearly 70,000 image files in them (sequential image upload from several webcams). I don't think FileZilla handled this too well.

I didn't think this would be a problem, because it shouldn't have been scanning for files, only directories. It froze just while expanding the D drive and never displayed any of the directories within it. After about 5 minutes of waiting I got a blue screen (my first time EVER under windows 2000, by the way) indicating a memory dump.

Bummer.

tashcrof@…

This has been around for a while. I was hoping it'd be fixed, but I guess no one reported or noticed it, so I think I will. :)

Pretty simple really, in the queue, the Status column's width is not saved. Every time I start FZ I have to reset it to not have a horizontal scroll bar.

Keep up the great work!

I help run a large Web site, and have been downloading the entire site to backup to CD. Right now I'm trying to download ~900MB from our main server, totaling several thousand files. Since FZ does not show a queue count (please add this!), I'm having to guess that the total is around 2,000-3,000 files.

Naturally, a transfer of this much data may not complete in one day, and I sure don't want to have to start over from scratch. Just downloading all of the directory listings takes about 10-15 minutes. So, I have been trying to export the queue.

I've tried exporting the entire queue of the ~900MB of files, and smaller portions of ~150MB, and whenever I try, FZ remains at 100% CPU usage, with memory usage continually fluctuating in small amounts. When I tried to export the 900MB queue, memory usage was around 96MB; when I tried the smaller one, it fluctuated more, from ~11MB to ~26MB, occasionally jumping to ~66MB.

I have FZ set to use XML, not the registry, and when I try to close FZ the same thing happens.

At first I had FZ set to use the registry, and when I tried to close it, the queue was so large, it ran the registry up to the max registry size, so I switched FZ to XML.

With the 900MB queue, I let FZ run at 100% CPU for around 15 minutes, which should certainly be enough on an Athlon XP 1700+ with 512MB of memory, don't you think? I mean, come on, what's a list of a few thousand files for a machine like that? :)

I think this is a fairly serious bug. If there's anything I can do to help the devs fix it, let me know.