Kicad crashing when selecting footprint on Symbol Properties window.

Bug #1785218 reported by Leandro Heck on 2018-08-03
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KiCad
Critical
Jeff Young

Bug Description

How to reproduce:

1 - Add any random text in the footprint field. For example, an old footprint name that is not on the libraries.

2 - Click the library symbol to select the footprint from the library.

Crash!

Application: kicad
Version: 6.0.0-rc1-unknown-ce37604~66~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-25-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Nick Østergaard (nickoe) wrote :

Could you try to add a backtrace?

tags: added: pcbnew
Download full text (6.2 KiB)

Sure

Reading symbols from kicad...(no debugging symbols found)...done.
(gdb)
(gdb) start
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n])
Starting program: /usr/bin/kicad
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe3c38700 (LWP 6630)]
[New Thread 0x7fffe3437700 (LWP 6631)]
[New Thread 0x7fffe2c36700 (LWP 6632)]
[New Thread 0x7fffe2435700 (LWP 6633)]
[Thread 0x7fffe2435700 (LWP 6633) exited]
[New Thread 0x7fffe2435700 (LWP 6635)]
[New Thread 0x7fffc9276700 (LWP 6636)]
[New Thread 0x7fffc8a75700 (LWP 6637)]
[New Thread 0x7fffc8274700 (LWP 6638)]
[New Thread 0x7fffc7a73700 (LWP 6639)]
[New Thread 0x7fffc7272700 (LWP 6640)]
[New Thread 0x7fffc6a71700 (LWP 6641)]
[New Thread 0x7fffc6270700 (LWP 6642)]
[New Thread 0x7fffc5a6f700 (LWP 6643)]
[New Thread 0x7fffc526e700 (LWP 6644)]
[New Thread 0x7fffc4a6d700 (LWP 6645)]

(kicad:6610): Gdk-CRITICAL **: 09:01:51.205:
IA__gdk_window_process_updates: assertion 'GDK_IS_WINDOW (window)' failed

(kicad:6610): Gdk-CRITICAL **: 09:01:51.205:
IA__gdk_window_process_updates: assertion 'GDK_IS_WINDOW (window)' failed
[New Thread 0x7fffc426c700 (LWP 6646)]
[New Thread 0x7fffc3a6b700 (LWP 6647)]
[Thread 0x7fffc426c700 (LWP 6646) exited]
[New Thread 0x7fffc326a700 (LWP 6648)]
[Thread 0x7fffc3a6b700 (LWP 6647) exited]
[Thread 0x7fffc326a700 (LWP 6648) exited]
[New Thread 0x7fffc2a69700 (LWP 6649)]
[New Thread 0x7fffc2268700 (LWP 6650)]
[Thread 0x7fffc2a69700 (LWP 6649) exited]
[Thread 0x7fffc2268700 (LWP 6650) exited]
[New Thread 0x7fffc1a67700 (LWP 6651)]
[Thread 0x7fffc1a67700 (LWP 6651) exited]
[New Thread 0x7fffc1a67700 (LWP 6652)]
[New Thread 0x7fffc2268700 (LWP 6653)]
[New Thread 0x7fffc2a69700 (LWP 6654)]
[Thread 0x7fffc2268700 (LWP 6653) exited]
[New Thread 0x7fffc326a700 (LWP 6655)]
[Thread 0x7fffc2a69700 (LWP 6654) exited]
[Thread 0x7fffc326a700 (LWP 6655) exited]
[New Thread 0x7fffc426c700 (LWP 6656)]
[New Thread 0x7fffc3a6b700 (LWP 6657)]
[Thread 0x7fffc426c700 (LWP 6656) exited]
[New Thread 0x7fffc1266700 (LWP 6658)]
[Thread 0x7fffc3a6b700 (LWP 6657) exited]
[New Thread 0x7fffc0a65700 (LWP 6659)]
[Thread 0x7fffc1266700 (LWP 6658) exited]
[New Thread 0x7fffbbfff700 (LWP 6660)]
[Thread 0x7fffc0a65700 (LWP 6659) exited]
[New Thread 0x7fffbb7fe700 (LWP 6661)]
[Thread 0x7fffbbfff700 (LWP 6660) exited]
[New Thread 0x7fffbaffd700 (LWP 6662)]
[Thread 0x7fffbb7fe700 (LWP 6661) exited]
[New Thread 0x7fffba7fc700 (LWP 6663)]
[Thread 0x7fffbaffd700 (LWP 6662) exited]
[New Thread 0x7fffb9ffb700 (LWP 6664)]
[Thread 0x7fffba7fc700 (LWP 6663) exited]
[Thread 0x7fffb9ffb700 (LWP 6664) exited]
[Thread 0x7fffc1a67700 (LWP 6652) exited]
[Thread 0x7fffe2c36700 (LWP 6632) exited]
[New Thread 0x7fffe2c36700 (LWP 6666)]
[New Thread 0x7fffb9ffb700 (LWP 6667)]
[Thread 0x7fffe2c36700 (LWP 6666) exited]
[New Thread 0x7fffba7fc700 (LWP 6668)]
[Thread 0x7fffb9ffb700 (LWP 6667) exited]
[New Thread 0x7fffbaffd700 (LWP 6669)]
[Thread 0x7fffba7fc700 (LWP 6668) exited]
[Thread 0x7fffbaffd700 (LWP 6669) exited]
[New Thread 0x7fffc426c700 (LWP 6670)]
[New Thread 0x7fffc3a6b700 (LWP 6671)]
[Thread 0x7...

Read more...

Nick Østergaard (nickoe) wrote :

Most of that is not really that relevant, the relevant parts appear when you write bt i the console. Only the last stack frame is shown in the above.

Jeff Young (jeyjey) wrote :

@Leandro & @Nick, no worries. It's easy enough to reproduce. I'll get on it.

Changed in kicad:
assignee: nobody → Jeff Young (jeyjey)
status: New → In Progress
importance: Undecided → Critical
milestone: none → 5.1.0
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 92b3aca0ef7a65cc8dcf52efb2070885b54c79d0
https://git.launchpad.net/kicad/patch/?id=92b3aca0ef7a65cc8dcf52efb2070885b54c79d0

Changed in kicad:
status: In Progress → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers