This problem is caused by a race condition in the socket class of FileZilla.
Happens if CSocket::Disconnect() get called between the worker thread's call to getaddrinfo and re-obtaining the lock. In that case the worker thread continues to connect and ultimately sets the socket state to connected, despite the previous call to Disconnect. The attached patch solves this problem. ** Attachment added: "socket.patch" http://launchpadlibrarian.net/37672584/socket.patch -- Filezilla crashed on file resuming https://bugs.launchpad.net/bugs/447224 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
