Custom Query (8142 matches)


Show under each result:

Results (202 - 204 of 8142)

Ticket Resolution Summary Owner Reporter
#12544 fixed hard crash - Faulting module name: libstdc++-6.dll mark

The filezilla logfile is empty, all i have is this in the windows eventlog:

Faulting application name: filezilla-server.exe, version:, time stamp: 0x00000000 Faulting module name: libstdc++-6.dll, version:, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x000000000001f70a Faulting process id: 0x5f8 Faulting application start time: 0x01d7b11f4c9119a6 Faulting application path: C:\Program Files\FileZilla Server\filezilla-server.exe Faulting module path: C:\Program Files\FileZilla Server\libstdc++-6.dll Report Id: e5e5db18-1fa7-11ec-8123-0026824f9497 Faulting package full name: Faulting package-relative application ID:

#12543 worksforme Poor startup performance for local folders having 10,000+ files Raptor

If the local folder (no matter it's located in HDD or external USB drive) selected contains more than 10,000 files (in my case 14,600 JPEGs, with average file size <1MB), I quitted the FileZilla client and re-opens again, it takes at least 5 minutes to see the interface (not even started to connect to any server). My iMac was idle at that moment (no other software using significant resources).

Can the startup performance be improved?

iMac (21.5-inch, Late 2013) CPU: 3.1GHz Quad-Core Intel i7 RAM: 16GB 1600MHz DDR3 HDD: 512GB SSD External HDD: HGST 5TB 2.5" HDD

#12542 fixed Critical error: Could not connect to server SHollands

I am unable to connect to the server. Commands are; Command: PASS * Response: 503 Bad sequence of commands Error: Critical error: Could not connect to server Status: Disconnected from server Status: Resolving address of Status: Connecting to Status: Connection established, waiting for welcome message... Status: Insecure server, it does not support FTP over TLS. Command: USER jgftpMars Response: 331 Password required Command: PASS * Response: 503 Bad sequence of commands Error: Critical error: Could not connect to server

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.