KICAD 8.0.4 crashes on macOS 14.2

Software
1

It crashes when assigning footprints

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               kicad [37120]
Path:                  /Applications/KiCad/KiCad.app/Contents/MacOS/kicad
Identifier:            org.kicad.kicad
Version:               8.0.4 (8.0.4)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2024-08-04 02:27:21.2898 +0800
OS Version:            macOS 14.2 (23C64)
Report Version:        12
Anonymous UUID:        34ED3B01-03E4-92A4-49EF-77CBBF1C1A18

Sleep/Wake UUID:       1D5CD7D2-35E4-4D24-97F7-EA14111C7E61

Time Awake Since Boot: 46000 seconds
Time Since Wake:       12360 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   kicad [37120]

Application Specific Information:
abort() called


Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x1807d60dc __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x18080dcc0 pthread_kill + 288
2   libsystem_c.dylib             	       0x180719a40 abort + 180
3   libc++abi.dylib               	       0x1807c5070 abort_message + 132
4   libc++abi.dylib               	       0x1807b5110 demangling_terminate_handler() + 320
5   libobjc.A.dylib               	       0x18045b99c _objc_terminate() + 160
6   libc++abi.dylib               	       0x1807c4434 std::__terminate(void (*)()) + 16
7   libc++abi.dylib               	       0x1807c7520 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 88
8   libc++abi.dylib               	       0x1807c7464 __cxa_throw + 308
9   _eeschema.kiface              	       0x135f258ac EESCHEMA_SETTINGS* SETTINGS_MANAGER::GetAppSettings<EESCHEMA_SETTINGS>() + 740
10  _eeschema.kiface              	       0x1368f5538 LIB_PIN::GetBoundingBox(bool, bool, bool) const + 76
11  _eeschema.kiface              	       0x1369101e8 LIB_SYMBOL::GetBodyBoundingBox(int, int, bool, bool) const + 544
12  _eeschema.kiface              	       0x1369f40d0 SCH_SYMBOL::doGetBoundingBox(bool, bool) const + 84
13  _eeschema.kiface              	       0x136ac48dc EE_SELECTION_TOOL::selectionContains(VECTOR2<int> const&) const + 168
14  _eeschema.kiface              	       0x136ac0ad0 EE_SELECTION_TOOL::Main(TOOL_EVENT const&) + 3468
15  _eeschema.kiface              	       0x136e0a4ac COROUTINE<int, TOOL_EVENT const&>::callerStub(long) + 60
16  _eeschema.kiface              	       0x136efb800 make_fcontext + 28

Thread 1:: com.apple.NSEventThread
0   libsystem_kernel.dylib        	       0x1807cd874 mach_msg2_trap + 8
1   libsystem_kernel.dylib        	       0x1807dfcf0 mach_msg2_internal + 80
2   libsystem_kernel.dylib        	       0x1807d64b0 mach_msg_overwrite + 476
3   libsystem_kernel.dylib        	       0x1807cdbf8 mach_msg + 24
4   CoreFoundation                	       0x1808ebbf4 __CFRunLoopServiceMachPort + 160
5   CoreFoundation                	       0x1808ea4bc __CFRunLoopRun + 1208
6   CoreFoundation                	       0x1808e99ac CFRunLoopRunSpecific + 608
7   AppKit                        	       0x1841f0510 _NSEventThread + 144
8   libsystem_pthread.dylib       	       0x18080e034 _pthread_start + 136
9   libsystem_pthread.dylib       	       0x180808e3c thread_start + 8

Thread 2:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        	       0x1807d89d4 __select + 8
1   CoreFoundation                	       0x180914e24 __CFSocketManager + 636
2   libsystem_pthread.dylib       	       0x18080e034 _pthread_start + 136
3   libsystem_pthread.dylib       	       0x180808e3c thread_start + 8

Thread 3:
0   libsystem_kernel.dylib        	       0x1807d106c __psynch_cvwait + 8
1   libsystem_pthread.dylib       	       0x18080e5fc _pthread_cond_wait + 1228
2   libc++.1.dylib                	       0x1807354dc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3   kicad                         	       0x100ab376c BS::thread_pool::worker() + 156
4   kicad                         	       0x100ab3b48 void* std::__1::__thread_proxy[abi:v15006]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (BS::thread_pool::*)(), BS::thread_pool*>>(void*) + 72
5   libsystem_pthread.dylib       	       0x18080e034 _pthread_start + 136
6   libsystem_pthread.dylib       	       0x180808e3c thread_start + 8

Thread 4:
0   libsystem_kernel.dylib        	       0x1807d106c __psynch_cvwait + 8
1   libsystem_pthread.dylib       	       0x18080e5fc _pthread_cond_wait + 1228
2   libc++.1.dylib                	       0x1807354dc std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 28
3   kicad                         	       0x100ab376c BS::thread_pool::worker() + 156
4   kicad                         	       0x100ab3b48 void* std::__1::__thread_proxy[abi:v15006]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (BS::thread_pool::*)(), BS::thread_pool*>>(void*) + 72
5   libsystem_pthread.dylib       	       0x18080e034 _pthread_start + 136
6   libsystem_pthread.dylib       	       0x180808e3c thread_start + 8
......
2

Mac in engineering?
Welcome to a world of pain.
Get another SSD and boot into Linux. Mint should be easy. Even boot into Win for max software choices.

3

Don’t want to stray too far off topic . . . but would be interesting to see the number of requests for help on this forum for Windows vs Mac vs Linux vs number of downloads of KiCad for Windows vs Mac vs Linux (perhaps Linux would be artificially under represented here as there are other ways of getting KiCad for Linux ?)

4

Can you reproduce this crash? If so, please file a bug report on gitlab (Help → Report Bug will do most of the work for you).

5

Yes, typically Linux programs are acquired thru distribution specific repositories.
Every distribution may have stats on hits for KiCAD,
Or…
The KiCAD repo may have hit stats on updates.

6

On topic first: if you can describe in detail what you were doing prior to the crash and attach the project you were working in, it will help others try and replicate the crash. (Probably not project-specific, but it does happen sometimes.) Making a Gitlab issue as mentioned above is great, please post a link to it here to make it easy to find.

(I may annoy the devs with this, but I create issues for every type of crash I get on the principle that either me or someone else will come across it and replicate it in the future.)

Off-topic second: I will be very surprised if there’s a useful measure of problem reports vs OS, mostly because the number of first time bug reporters is relatively low and the distribution of high frequency bug reporters across OS is unlikely to be representative. Fwiw, every OS (and in Linux-world, every window manager) has its own set of bugs and oddities, and I’m not sure it is helpful advice to recommend a new OS off the bat without any info beyond a single crash report.

7

There’s are lots of Mac users on this forum, and no shortage of Linux issues with Kicad.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.