Opened 15 years ago

Last modified 15 years ago

#3529 closed Bug report

Drag&Drop image from Firefox sometimes results empty file

Reported by: aggro80 Owned by:
Priority: normal Component: Other
Keywords: Cc: aggro80, Tim Kosse
Component version: Operating system type:
Operating system version:


If I drag&drop an image from a website to Filezilla to be uploaded to the ftp-server the image sometimes uploads correctly, but about 50% of the times the file ends up being empty. Size 0 bytes. It is empty also, when looking or opening it from the server's filesystem.

This happened on two computers (which are nearly identical)

FTP client: Filezilla 3.0.10
FTP server: FileZilla Server version 0.9.24 beta (but seems to happen with other servers also)
OS: Windows XP Professional, SP2

The image that was dragged:

But it seems to happen with any image that can be dragged.

Attachments (1)

ftplogs.txt (8.8 KB ) - added by aggro80 15 years ago.
FTP client and server logs

Download all attachments as: .zip

Change History (3)

by aggro80, 15 years ago

Attachment: ftplogs.txt added

FTP client and server logs

comment:1 by Tim Kosse, 15 years ago

I cannot reproduce this, Firefox does not even allow me to drag images to FileZilla at all.

comment:2 by aggro80, 15 years ago

codesquid: Did you test with Windows XP Professional SP2, Firefox and Filezilla 3.0.10 also? I think this works only in Windows.

Do you have any idea (or possibility to test) what file path Firefox provides from the drag&drop event assuming you get it to working. I'm wondering whether the path points to an existing temp file that was generated when the page was loaded. Or does it point to a new file, which is generated on-fly right after mouse button is released. That would explain why the file is sometimes empty and sometimes correct. Just a matter of which process gets processor time first when the event occurs.

I also wonder does the GetSize() return an error code in state.cpp which could be used to identify this problem. Should the return value be checked for that function call anyway to print errors if that happens? Adding such check might also help solving this bug.

"wxULongLong GetSize() const

static wxULongLong GetSize(const wxString& filename)

Returns the size of this file (first form) or the size of the given file (second form). If the file does not exist or its size could not be read (because e.g. the file is locked by another process) the returned value is wxInvalidSize."

Note: See TracTickets for help on using tickets.