Opened 4 years ago

Closed 4 years ago

Last modified 3 years ago

#12100 closed Bug report (worksforme)

FileZilla crashes on launch and newest version can't be opened

Reported by: fmconti Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: All Operating system type: OS X
Operating system version: 10.14.6


FileZilla 3.45.1 was the only version I could start on my Mac, but now it crashes on launch. At the bottom of the message there is the report.
All other newer versions, after installation, return the message "The application could not be opened"

Crash Report
Process: filezilla [2641]
Path: /Users/USER/Desktop/
Identifier: org.filezilla-project.filezilla
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: filezilla [2641]
User ID: 501

Date/Time: 2020-01-30 09:59:52.787 +0100
OS Version: Mac OS X 10.14.6 (18G2022)
Report Version: 12
Anonymous UUID: 01707240-4EEC-3652-E2D3-4CF3A5C4FA75

Time Awake Since Boot: 1200 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2):

TEXT 0000000105cd8000-00000001067c9000 [ 10.9M] r-x/rwx SM=COW

Thread 0 Crashed:
0 0x000000010e54c000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffee9f27bc8

r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000

r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010e54c000 rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0

Binary Images:

0x105cd8000 - 0x1067c8ff7 + (0) <2AA5D23A-5618-3011-9FE0-EB563ED44B45>
0x10e54b000 - 0x10e5b570f + (655.1.1) <B3D9DDCB-5AA7-3674-9608-16B5AA4AA494>

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 0
thread_create: 0
thread_set_state: 0

Calls made by this process:

task_for_pid: 0
thread_create: 0
thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 489
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=13.9M resident=0K(0%) swapped_out_or_unallocated=13.9M(100%)
Writable regions: Total=8500K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8500K(100%)


REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Stack 8192K 1
DATA 1016K 4
TEXT 11.4M 2
shared memory 8K 2
=========== ======= =======
TOTAL 78.9M 12

Model: iMac18,3, BootROM, 4 processors, Intel Core i5, 3,8 GHz, 16 GB, SMC 2.41f1
Graphics: kHW_AMDRadeonPro580Item, Radeon Pro 580, spdisplays_pcie_device, 8 GB
Memory Module: BANK 0/DIMM0, 8 GB, DDR4, 2400 MHz, 0x80AD, 0x484D413831475336414652384E2D554820202020
Memory Module: BANK 1/DIMM0, 8 GB, DDR4, 2400 MHz, 0x80AD, 0x484D413831475336414652384E2D554820202020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16F), Broadcom BCM43xx 1.0 ( AirPortDriverBrcmNIC-1305.9)
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE HDD ST3000DM001, 3 TB
USB Device: USB 3.0 Bus
USB Device: External USB 3.0
USB Device: My Book 1234
USB Device: M3 Portable
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
Thunderbolt Bus: iMac, Apple Inc., 41.1

Change History (4)

comment:1 by Tim Kosse, 4 years ago

Resolution: worksforme
Status: newclosed

Make sure to use the built-in functionality of macOS to extract the archive. Using third-party tools to extract the archive will damage the contained application bundle.

comment:2 by fmconti, 4 years ago

I followed your instructions and I solved the problem. Thank you

comment:3 by Tony Lima, 3 years ago

This fixed my problem. Suggestion: put this information in the error box.

Tony Lima

comment:4 by Tim Kosse, 3 years ago

The error box comes from macOS itself, we cannot influence what is written in it.

Note: See TracTickets for help on using tickets.