Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#11227 closed Bug report (rejected)

FileZilla crashes when I download

Reported by: theosam Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: Windows 10 Home

Description

FileZilla crashes every time I try to download something from a server to my computer.

Attachments (1)

filezilla.log (38.7 KB ) - added by theosam 3 years ago.
logfiel

Download all attachments as: .zip

Change History (15)

by theosam, 3 years ago

Attachment: filezilla.log added

logfiel

comment:1 by Tim Kosse, 3 years ago

Status: newmoreinfo

There should be a FileZilla crash dump in the %LOCALAPPDATA%/CrashDumps directory, please attach it to this ticket.

Last edited 3 years ago by Tim Kosse (previous) (diff)

comment:2 by theosam, 3 years ago

Status: moreinfonew

Hi, I can't cause they are all bigger than 1 MB. Can I send them via email?

comment:3 by Tim Kosse, 3 years ago

Yes: tim.kosse@…

comment:4 by Tim Kosse, 3 years ago

Resolution: rejected
Status: newclosed

You're using a faulty third-party shell extension. Please remove MysticThumbs64.dll

comment:5 by mysticcoder, 3 years ago

developer of mysticthumbs here. can you elaborate on how it causes filezilla to crash? it's not a common thing so there's an interop problem here. please email me.

in reply to:  5 comment:6 by theosam, 3 years ago

Replying to mysticcoder:

developer of mysticthumbs here. can you elaborate on how it causes filezilla to crash? it's not a common thing so there's an interop problem here. please email me.

Hi... would you like to have the FileZilla crash dump as well? If so, please give me an email where I can send it.
Or was that comment not meant for me?

comment:7 by mysticcoder, 3 years ago

Yeah, was meant for the FileZilla team to cross communicate. Send me the crash dump anyhow so I can see if there's anything obvious. Please use the contact page at mysticcoder.net to create a ticket. Be sure to attach the dump file. Thanks

Last edited 3 years ago by mysticcoder (previous) (diff)

comment:8 by theosam, 3 years ago

That doesn't work cause they are all bigger than 1 MB

comment:9 by mysticcoder, 3 years ago

The internet is still juvenile unfortunately and I don't want to reveal email addresses here for spam protection. Can you share via dropbox or similar?

comment:10 by mysticcoder, 3 years ago

contact me via the website so we can create a private thread anyhow. we'll sort it out there.

comment:11 by Tim Kosse, 3 years ago

mysticcoder: Due to its size I deleted the dump after processing.

Please have a look at https://forum.filezilla-project.org/viewtopic.php?f=2&t=41889&p=150094#p150094 at a different issue with your shell extension.

Basically, I think you need to split your extension into two parts: The actual shell extension and a service that generates the icons, with the two communicating via a dead simple IPC mechanism. That way nothing fancy is going on inside the shell extension that can interfere with other programs.

comment:12 by mysticcoder, 3 years ago

Wouldn't an IPC be something fancy in itself?
In any case, thanks for the stack trace and comments. It's to do with generating HTML thumbs most likely by the look of it. Uses a IE window to render which requires some message pumping filth. May be time to revoke that support.

comment:13 by Tim Kosse, 3 years ago

Wouldn't an IPC be something fancy in itself?

Not really, IPC is commonly used by shell extensions. Moving the actual work into a daemon also keeps the size and memory consumption of the shell extension low, which is very useful if it is loaded in hundreds of running processes. The main challenge if using a daemon is in isolating users and permission, in your case lest user A create icons for files only accessible by user B.

comment:14 by mysticcoder, 3 years ago

The dll is shared in any case. memory is constant surely. the DLL IS the daemon. Isn't that the point of DLL's? IPC a message to some other task to process and return a result, what's the difference? May as well stay in the dll. The problem with this case is that rendering HTML thumbs uses "way out there" techniques that obviously can cause issues when running synchronously in some tasks. I may have to consider removing small icon support for html and any other format that has compound complexity.

Note: See TracTickets for help on using tickets.