macOS Sierra - Crash after any transfer

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
chris-hn
500 Command not understood
Posts: 3
Joined: 2018-11-29 12:07

macOS Sierra - Crash after any transfer

#1 Post by chris-hn » 2018-11-29 12:54

So Filezilla worked fine for years on my mac and forever on the Sierra but I think I've broken something today after I installed a newer version of nano if that's all related, with brew, I kept the log mentioning ncurses (I've attached the terminal output during that install).. Everything else works on the mac fine, it was up for a few days, used FileZilla loads yesterday and when I tried today it finishes the transfer (SFTP or FTP, either direction, various servers) and the window disappears. This is version 3.38.1 tried the RC one, same crash. I checked console logs and I see the following but I'm not sure if they're a new thing as I've never had problems with filezilla on the mac before (including previous versions).

In the console log against the filezilla process I see

Code: Select all

UNIX error exception: 17 
and also

Code: Select all

Sandbox: filezilla(1751) System Policy: deny(2) file-write-unlink /Users/<me>/Library/Saved Application State/org.filezilla-project.filezilla.savedState/restorecount.plist
and/or

Code: Select all

nw_path_close_fd Failed to close guarded necp fd 19 [9: Bad file descriptor]
and

Code: Select all

LSExceptions shared instance invalidated for timeout.
I've tried clearing the filezilla install with appcleaner but that didn't make any difference. I've also rebooted to see if any temporary environment vars were changed by the brew install but that didn't help. The brew install is the only think I can think of anyway. But if the new nano works (it does) and it required installing new libraries I fear something must have changed?

I've changed logging to be to a file and that setting is preserved across crashes but I have to change debug to 4 then reproduce in order to get more info in the log which doesn't look very informative (so it's the macos killing it I imagine?)
This is close to the end after connecting and changing dir:

Code: Select all

2018-11-29 12:50:12 4251 2 Response: New directory is: "/var/www"
2018-11-29 12:50:12 4251 2 Trace: CSftpChangeDirOpData::ParseResponse() in state 2
2018-11-29 12:50:12 4251 2 Trace: CControlSocket::ResetOperation(0)
2018-11-29 12:50:12 4251 2 Trace: CSftpChangeDirOpData::Reset(0) in state 2
2018-11-29 12:50:12 4251 2 Trace: CSftpFileTransferOpData::SubcommandResult(0) in state 1
2018-11-29 12:50:12 4251 2 Trace: CControlSocket::CheckOverwriteFile()
2018-11-29 12:50:19 4251 2 Trace: CControlSocket::SendNextCommand()
2018-11-29 12:50:19 4251 2 Trace: CSftpFileTransferOpData::Send() in state 4
2018-11-29 12:50:19 4251 2 Command: get "stats.sql" "/Users/<me>/Documents/workspace/stats.sql"
2018-11-29 12:50:19 4251 2 Command: remote:/var/www/stats.sql => local:/Users/<me>/Documents/workspace/stats.sql
2018-11-29 12:50:19 4251 2 Trace: CSftpFileTransferOpData::ParseResponse() in state 4
2018-11-29 12:50:19 4251 2 Trace: CControlSocket::ResetOperation(0)
2018-11-29 12:50:19 4251 2 Trace: CSftpFileTransferOpData::Reset(0) in state 4
2018-11-29 12:50:19 4251 2 Status: File transfer successful, transferred 7.6 KB in 1 second
2018-11-29 12:50:19 4251 2 Trace: CFileZillaEnginePrivate::ResetOperation(0)
2018-11-29 12:50:19 4251 2 Trace: CFileZillaEnginePrivate::ResetOperation(0)
2018-11-29 12:50:19 4251 2 Trace: CControlSocket::DoClose(66)
2018-11-29 12:50:19 4251 2 Trace: CControlSocket::ResetOperation(66)
2018-11-29 12:50:19 4251 2 Trace: CFileZillaEnginePrivate::ResetOperation(66)
2018-11-29 12:50:19 4251 2 Trace: CControlSocket::DoClose(66)
2018-11-29 12:50:19 4251 1 Trace: CControlSocket::DoClose(66)
2018-11-29 12:50:19 4251 1 Trace: CControlSocket::ResetOperation(66)
2018-11-29 12:50:19 4251 1 Trace: CFileZillaEnginePrivate::ResetOperation(66)
2018-11-29 12:50:19 4251 1 Trace: CControlSocket::DoClose(66)
Attachments
breaking ncurses.txt
(3.14 KiB) Downloaded 12 times

User avatar
botg
Site Admin
Posts: 31605
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: macOS Sierra - Crash after any transfer

#2 Post by botg » 2018-11-29 14:06

The error messages do not come from FileZilla. FZ doesn't even touch the mentioned file.

It appears you may have damaged your operating system files. Try to undo everything you did to damage the system. If the problem persists, format your hard-disk and start over with a fresh operating system install.

chris-hn
500 Command not understood
Posts: 3
Joined: 2018-11-29 12:07

Re: macOS Sierra - Crash after any transfer

#3 Post by chris-hn » 2018-11-29 14:09

Very last resort.. These files seem to be created and touched every time I run or do something in FileZilla but they get modified and so on so it's not like I don't have access. Tried deleting and everything, they just get recreated fine.. I dread using a sftp client without remote and local explorer this is an absolute nightmare!

User avatar
botg
Site Admin
Posts: 31605
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: macOS Sierra - Crash after any transfer

#4 Post by botg » 2018-11-29 14:10

It's the operating system itself creating these files, FileZilla has no influence on this.

chris-hn
500 Command not understood
Posts: 3
Joined: 2018-11-29 12:07

Re: macOS Sierra - Crash after any transfer

#5 Post by chris-hn » 2018-11-29 15:10

Well whatever it was uninstalling FortiClient, manually nuking the plist found by AppCleaner and deleting the temp file dir mentioned in console didn't seem to work on its own (across reboots as well whatever that's worth)

BUT - what did work was I moved my ~/.config/filezilla dir, opened FileZilla and it wasn't crashing. I managed to restore all settings saved into the newly created config dir and it's still not crashing. If however I restore the previous filezilla config dir, the crash is back. (And if I do the switcheroo again to the new filezilla config dir with the freshly restored conig, its not crashing again). The window positions and sort options I have for the explorers have not been preserved if that means anything (not sure if they're saved at all). Anyway don't stop working on FileZilla I was having proper panic attacks at the prospect of not having it available lol

Post Reply