pcbnew crashed moving footprint

[Shareef Jalloq]

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.

Shareef.

Application: kicad
Version: (5.0.0-3-g5ebb6b6), release build
Libraries:
    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:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[Shareef Jalloq (shareef)]

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)]

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

[Shareef Jalloq (shareef)]

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)]

@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.

[Jeff Young (jeyjey)]

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.