#8305 closed Bug report (fixed)
FileZilla process does not terminate on exit
Reported by: | johnnyfv | Owned by: | |
---|---|---|---|
Priority: | critical | Component: | FileZilla Client |
Keywords: | Cc: | ||
Component version: | Operating system type: | Windows | |
Operating system version: | Windows 7 |
Description
My install of FileZilla just updated (to 3.6.0). To reproduce the bug: open an SFTP site, exit out of FileZilla, then open Windows Task Manager. Both 'filezilla.exe' and 'fzsftp.exe' remain running.
I call FileZilla from a VBScript, and my program continues only after exiting FileZilla. After installing the latest version, exiting FileZilla did not allow my process to continue.
Opening Windows Task Manager, it became evident that closing the FileZilla interface does *not* halt 'filezilla.exe' or 'fzsftp.exe'; both of these remain resident in memory despite exiting-out of FileZilla.
Opening FileZilla manually and connecting to an SFTP site causes the same behavior. The behavior only manifests if an SFTP site is opened.
Change History (6)
comment:1 by , 12 years ago
Priority: | critical → high |
---|
comment:3 by , 12 years ago
Status: | moreinfo → new |
---|
I can reproduce this with version 3.6.0.2, in particular if a prompt about an unknown certificate has been shown during the session. Minimizing FileZilla to tray is disabled.
Maybe it is same problem johnnyfv has?
comment:4 by , 12 years ago
Priority: | high → critical |
---|
This bug still exists in version 3.6.0.2.
To reproduce:
- Connect to an SFTP server (without caching the host key; not sure if caching changes behavior)
- Exit out of FileZilla interface
- Check Windows Task Manager - both 'filezilla.exe' and 'fzsftp.exe' processes remain running. Re-opening FileZilla and reconnecting results in multiple instances.
'Minimize to tray' in unchecked in Interface Settings.
Having a rogue app that won't close on exit seems like a critical/security relevant bug to me.
comment:5 by , 12 years ago
I can confirm the bug (Filezilla 3.6.0.2, windows XP).
Connecting to a sftp server makes the filezilla process to remain running in the background if the server key is not stored in the cache before to initiate the connection.
This means that the first time you connect to an sftp server you are pretty sure to have the problem.
This is a real problem is you connect to a lot of sftp servers from a computer which is not rebooted often. (The number of processes running in the background may becomes high)
comment:6 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
A fix for this bug has since been committed to the repository and will be available in the next version.
Only security relevant bugs are considered "critical".