Segmentation fault after a failed assertion when "Cleanup Tracks and Vias" in Pcbnew

Bug #1823973 reported by Paul van der hoeven on 2019-04-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Critical
Tomasz Wlostowski

Bug Description

KiCad V5.1.0+dfsg1 gets a "failed assertion" when clicking on:
> Pcbnew / Edit / Cleanup Tracks and Via's.

The backtrace shows:
ASSERT INFO:
/build/kicad-PCtFts/kicad-5.1.0+dfsg1/pcbnew/tracks_cleaner.cpp(363): assert "connectivity->GetConnectivityAlgo()->ItemEntry( aTrack ).GetItems().size() != 0" failed in testTrackEndpointDangling().

BACKTRACE:
[1] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[2] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[3] wxEvtHandler::TryHereOnly(wxEvent&)
[4] wxEvtHandler::DoTryChain(wxEvent&)
[5] wxEvtHandler::ProcessEvent(wxEvent&)
[6] wxWindowBase::TryAfter(wxEvent&)
[7] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[8] wxMenuBase::SendEvent(int, int)
[9] g_closure_invoke
[10] g_signal_emit_valist
[11] g_signal_emit
[12] gtk_widget_activate
[13] gtk_menu_shell_activate_item
[14] g_signal_emit_valist
[15] g_signal_emit
[16] gtk_main_do_event
[17] g_main_context_dispatch
[18] g_main_loop_run
[19] gtk_main
[20] wxGUIEventLoop::DoRun()
[21] wxEventLoopBase::Run()
[22] wxAppConsoleBase::MainLoop()
[23] wxNavigationEnabled<wxTopLevelWindow>::RemoveChild(wxWindowBase*)
[24] wxEntry(int&, wchar_t**)
[25] wxNavigationEnabled<wxTopLevelWindow>::RemoveChild(wxWindowBase*)
[26] __libc_start_main
[27] _start

**** Full version info: ****

Application: kicad
Version: 5.1.0+dfsg1-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.36.0 librtmp/2.3
Platform: Linux 4.19.0-4-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.64.0
    Compiler: Clang 7.0.1 with C++ ABI 1002

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

****

On my system this is triggered every time in the "Highpower-Mechaduino" project.
I zipped the whole project and uploaded it to the KiCad users forum:
https://forum.kicad.info/t/kicad-5-1-crashes-often/16232/13?u=paulvdh

Direct link to the zipped project:

https://kicad-info.s3.dualstack.us-west-2.amazonaws.com/original/2X/9/9b29de1e9c5628c4c063f82109693d1a326f5645.zip

Changed in kicad:
assignee: nobody → Tomasz Wlostowski (twlostow)
Changed in kicad:
status: New → Triaged
importance: Undecided → High
importance: High → Critical
tags: added: pcbnew
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers