Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#11254 closed Bug report (rejected)

OS crash on Mac using any recent FileZilla build

Reported by: stevepodradchik Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: 3.25.2 Operating system type: OS X
Operating system version: 10.12.4


For > 1 year, loading a directory list causes a crash in Mac OS. Installed multiple OS updates, multiple FileZilla updates, etc. Crash generally happens on directory listing but sometimes takes opening a few directories before the crash happens. I would also note that NO OTHER APP causes anything like this and I am a software developer so please do not blame the OS -- just workaround any OS issue if there is one. Very, very easy to repro. Let me know if you need more info but I think the Mac version, Mac OS version, and FileZilla version are included here. The only 3rd party kexts is the Forinet security/VPN client and .. no .. removing it does NOT make any difference (tried that).

Anonymous UUID: 18660DFD-BB2A-7402-F6D2-3579BA9CA2C0

Mon May 8 13:44:42 2017

* Panic Report *
panic(cpu 2 caller 0xffffff7fa7444aa9): "sfree on invalid allocation at 0xffffff8049b87200"@/BuildRoot/Library/Caches/
Backtrace (CPU 2), Frame : Return Address
0xffffff812f83bd30 : 0xffffff80266ec3ec
0xffffff812f83bdb0 : 0xffffff7fa7444aa9
0xffffff812f83bde0 : 0xffffff7fa7442375
0xffffff812f83bed0 : 0xffffff8026d1edb8
0xffffff812f83bf50 : 0xffffff8026c25695
0xffffff812f83bfb0 : 0xffffff802669dd46

Kernel Extensions in backtrace:[CDBEAC20-BD05-3DF5-B7D3-51C3E8DCF872]@0xffffff7fa7439000->0xffffff7fa7458fff


BSD process name corresponding to current thread: cloudphotosd

Mac OS version:

Kernel version:
Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64
Kernel UUID: 06F94FD7-451F-34A1-B13C-D68FF7EDE0A0
Kernel slide: 0x0000000026400000
Kernel text base: 0xffffff8026600000
HIB text base: 0xffffff8026500000
System model name: MacBookAir5,2 (Mac-2E6FAB96566FE58C)

System uptime in nanoseconds: 94841157106
last loaded kext at 40807836026: com.fortinet.fct.kext.fctapnke 1 (addr 0xffffff7fa980c000, size 516096)
loaded kexts:
com.fortinet.fct.kext.fctapnke 1 6.0.1 92 1.70 3.0 8.0.1 2.7.0d0 110.23.17 1.0.0 131 3.14.41 3.6.4 279.48 1 279.48 10.2.4 1 1.0.1 5.0.4f18 7.0.0 3.0.8 1 3.1 279.48 10.2.4 4.0.0 208 4.1.0 1.0.0 1.0.0 3.14.41 170.9.14 1.3.1 5.0.4f18 394.50.1 252 252 252 404.50.6 404.50.6 540.30.1 3.0.1 1.0.0d1 1.0.0 40 366.50.19 295.20.1 800.20.24 1150.9.1a2 326 1.8 161.0.0 5.0 2.0 2.1 5.0 1.7 219.0.0 172 3 8 219.0.0 5.0.4f18 368.14 76.6 1.0 279.48 525 159.6 11 1.0 4.1.1 5.0.2 311.11 3.14.41 279.48 279.48 205.15 1.2.0 1.0.0 1.0.0 1.0.0 6.0.0d8 1.0.14d1 3.14.41 1.1.0 514.10 3.1.9 1.0.18d1 514.10 199 5.0.4f18 5.0.4f18 5.0.4f18 5.0.4f18 258 1.1 4.0.4 394.50.1 131.50.1 394.50.1 5.0.0 5.0.0 1.1 1.1 540.30.1 1 5.0.2 5.0.2 2.1.2 3 4.5.3 6.5.6 900.4.1 1200.12.2 1.0.1b8 3.2 1.0.4 288 1.1 1.1 1.1 1.1 1.0 900.4.1 1.1 2.1 2.0 2.0.0 1.1 300.0 1.0.0d1 2 1.0.5 1.0 1 1.1 1.0 444.50.16 2.1 31 28.30 5.0 2.9 1.4 1 1 1.0
Model: MacBookAir5,2, BootROM MBA51.00EF.B0C, 2 processors, Intel Core i7, 2 GHz, 8 GB, SMC 2.5f9
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434353153364D465238412D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434353153364D465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (
Bluetooth: Version 5.0.4f18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM512E, 500.28 GB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 2.0 Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 3.0 Bus
USB Device: iPhone
Thunderbolt Bus: MacBook Air, Apple Inc., 23.4

Change History (5)

comment:1 by Tim Kosse, 6 years ago

Resolution: rejected
Status: newclosed

com.fortinet.fct.kext.fctapnke 1

That's your problem. The fortinet snake oil is rancid. Please uninstall this placebo and hire a real doctor.

comment:2 by stevepodradchik, 6 years ago

Wow! Thanks for being a complete jerk. You apparently missed the part about removing FortiNet did NOT resolve the issue. Do you ever get out in the real world and talk to humans?

Rather, I'm uninstalling FileZilla from all our corporate machines and using an app that works and doesn't have people like you maintaining it.


comment:3 by Tim Kosse, 6 years ago

According to the crash log the FortiNet kernel extension is still loaded, it has not been removed.

comment:4 by stevepodradchik, 6 years ago

Correct. I put it back in because I need it for a work VPN and removing it has NOT made any difference in the past (and it's a bit of a pain to put back once removed).

If I remove it and still get the crash, will you or someone look at the bug and not close it out of hand?

Thanks, Steve

comment:5 by Tim Kosse, 6 years ago

I can have a look at the clean dump, though I won't be able to do anything with it.

A fundamental design aspect of modern operating system is process separation to prevent one process from crashing the entire system. In your case, FileZilla does something that crashes your entire system. This means that there must be an underlying fault in your system (be it kernel, drivers or hardware) that results in this this design principle violation.

The most common cause for system crashes are faulty third-party drivers and kernel extensions. Nearly all reported system crashes show at least one loaded third-party kernel extension, making them the most likely culprit.

Analyzing MacOS crashes is Apple's responsibility, you need to contact them. They'll probably ask you to remove all third-party kernel extensions, if they reply at all. If the problem then goes away if not using any third-party kernel extensions then it must be reported to the kerel extension vendor.

That said, the fortinet kernel extensions are known to be highly problematic and a leading cause for MacOS system crashes.

Note: See TracTickets for help on using tickets.