Kodi Community Forum

Full Version: Crashing
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I have been using Kodi back when it was XBMC.
but for some reason i cant get it to work anymore.i tried to install KODI 17.1 but it crashes when I try to open it.
and now I have to go back all the way to KODI 14.2 to get anything that works even though I was just using Jarvis
Can anyone help this is what the crash report says.




Process: launchd [4049]
Path: /Applications/Kodi.app/Contents/MacOS/Kodi
Identifier: org.xbmc.kodi
Version: Huh (Huh)
Code Type: X86-64 (Native)
Parent Process: launchd [141]

Date/Time: 2017-04-10 18:36:09.715 -0500
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9

Interval Since Last Report: 8428544 sec
Crashes Since Last Report: 832
Per-App Crashes Since Last Report: 98
Anonymous UUID: 86E813D4-9561-4144-85E0-BCCF8F965FB9

Crashed Thread: Unknown

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fff5fc01028

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 2

Binary images description not available


External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
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: 8961
thread_create: 0
thread_set_state: 0

Model: Macmini5,1, BootROM MM51.0077.B14, 2 processors, Intel Core i5, 2.3 GHz, 4 GB, SMC 1.76f0
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE4), Broadcom BCM43xx 1.0 (5.106.198.19.22)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: My Book 1110, 0x1058 (Western Digital Technologies, Inc.), 0x1110, 0xfa120000 / 4
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8281, 0xfa113000 / 7
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: My Book 1230, 0x1058 (Western Digital Technologies, Inc.), 0x1230, 0xfd120000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
Moved to Mac OS X.
IIRC Krypton requires OS X 10.8 or newer.
I'm running 10.12.1 and am encountering this same issue.
(2017-04-11, 02:37)Tinwarble Wrote: [ -> ]Moved to Mac OS X.
I installed IOS 10.12.4 and still nothing
Try http://forum.kodi.tv/showthread.php?tid=311058 or post a Debug log (wiki) if it doesn't solve the issue.
The initial issue you posted was due to a to old osx version as already pointed out. Any other issues which prevent kodi from starting on newer osx versions have a different cause and need a new log for figuring it out (or at least a better error description from your side).
(2017-04-11, 22:20)Memphiz Wrote: [ -> ]The initial issue you posted was due to a to old osx version as already pointed out. Any other issues which prevent kodi from starting on newer osx versions have a different cause and need a new log for figuring it out (or at least a better error description from your side).

Thank you Memphiz! Although the fix looked technical, it was really simple once i figure out what Console and Terminal were. Thank you!