FileBot

Hi Everyone,

The current version of Filebot 4.7.2 keeps crashing and hanging on Mac OS Sierra 10.12 Beta (16A313a) Public Beta 7 and it also then crashes other apps on the mac as well. Can you please update Filebot with Sierra support so it doesnt crash when renaming files on my synology server?

Thank-you,

Shawn

Do have any logs? Does it crash before startup? Or does the UI show up and then hang? Does it work for local files but not remote files?

If Sierra breaks apps then I'd report the issue to Apple and wait for the next beta. I'll look into it, but I'm not sure if it's something i can fix on my side.

I am having the same issue on the final release of Mac OS Sierra.

The UI starts up and it names ok on local disks, but when I try and rename a file on my Synology NAS, it asks me to add permissions by dragging the folder across, renames the file then just stops and isn't responsive anymore. Even if I force quite the application it then doesn't startup again and I have to power boot my MAC

Have you tried a different network share protocol?

* If you're using SMB try AFP instead.
* If you're using AFP try SMB instead.
* Have you tried uninstall & reinstall via the App Store?

From FileBot's point of view, local files are the same as remote files so this issue can't be fixed in the FileBot code and is probably an OS issue.

The macOS filesystem abstraction layer might still be a bit buggy, so future a macOS update might fix this issue. If you have any system crash logs you could send them to Apple.

Hi.
I can confirm, that FileBot kills the Mac completly under macOS Sierra when I try to rename Files on my NAS.
However, nothing happens when I connect to it via SMB.
Do I connect via AFP it takes 1 Second to freeze nearly everything. Only a hard reset helps in that case.

Please report the issue to Apple and the NAS manufacturer: https://developer.apple.com/bug-reporting/

Providing the SMB/AFP virtual filesystem layer is the responsibility of the OS. Nothing FileBot can do about that. FileBot only sees "local" files but how filesystem operations translate to disk read/write or network requests is entirely up to the OS.

Try tweaking your SMB/AFP settings on your NAS and try Google. Might be a common issue with that NAS (you didn't say which one so I can't help you there).

Oh, sorry. The NAS is a Synology DS216+

Seems to be a Synology issue: https://forum.synology.com/enu/viewtopic.php?t=122975

I'm having the same problems with my Netgear ReadyNAS devices as well so It's not limited to Synology only, I've switched to SMB (instead of AFP) and the problem seems to have gone away - thanks for the suggestion RedNoah.