pcbnew crashed moving footprint

Bug #1786349 reported by Shareef Jalloq on 2018-08-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Jeff Young

Bug Description

I'm running MacOS 10.13.6 with the following version of KiCAD. I just had the tool crash on me while I was trying to move a component in pcbnew. I've also attached the MacOS crash dump if that's useful. The version I'm running is the pre-built DMG.

I'm new to KiCAD and this is the first time I've used pcbnew so can't comment on repeatability.


Application: kicad
Version: (5.0.0-3-g5ebb6b6), release build
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
Platform: Mac OS X (Darwin 17.7.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.51.0
    Compiler: Clang 8.0.0 with C++ ABI 1002

Build settings:

Tags: osx Edit Tag help
Shareef Jalloq (shareef) wrote :
Adam Wolf (adamwolf) on 2018-08-10
tags: added: osx
Shareef Jalloq (shareef) wrote :

Another bit of information that might be relevant. When I say I was moving a component, I was hovering over a component and hit the 'M' key to begin a move. That's when it crashed.

Seth Hillbrand (sethh) wrote :

Were you editing zones just before this? Also, is there a zone behind the component you were moving?

Shareef Jalloq (shareef) wrote :

Given I just had to look up what you meant by zones, no. You mean plane fill areas?

This was a brand new layout with only the components placed. I had only just started moving them out from their centre clumping.

Jeff Young (jeyjey) wrote :

@Seth I noticed the other day when tracking down another bug that there's something weird going on with the POINT_EDITOR: it's main loop seems to run every time there's a selection change event.

Changed in kicad:
importance: Undecided → Critical
Jeff Young (jeyjey) on 2018-09-13
summary: - pcbnew crashed on MacOS
+ pcbnew crashed moving footprint
Jeff Young (jeyjey) wrote :

We don't know a lot here, but I think the error log tells us:

1) it crashes on a null pointer access
2) it is in a co-routine which takes a TOOL_EVENT as a parameter
3) the null pointer access is quite near the beginning of the routine

There are 4 routines that fit that description; one of them makes not pointer dereferences and one of which check all pointers near the start.

I've added extra safety checks to the other two.

Jeff Young (jeyjey) on 2018-09-17
Changed in kicad:
assignee: nobody → Jeff Young (jeyjey)
status: New → In Progress
Jeff Young (jeyjey) on 2018-09-17
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.

Other bug subscribers

Bug attachments