KiCad

Symbol editor crashes in different situations

Bug #1828801 reported by eelik on 2019-05-13

10

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	KiCad	Fix Committed	Critical	Unassigned	KiCad 6.0.0-rc1

Bug Description

I've got more than one seemingly random crashes within short time. I couldn't reproduce one, but the information from drmingw is similar to another one which is here. Unfortunately I can't remember the exact steps, although once I just opened a symbol in the symbol editor, clicked on the canvas and it crashed.

kicad.exe caused an Access Violation at location 0000000004B81AC2 in module _eeschema.kiface Reading from location 0000000000000008.

AddrPC Params
0000000004B81AC2 0000000004EF19E0 0000000004EF37D0 0000000012AB2810 _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000004BE8083 00000000206981F8 000007FEFD5910C8 000000000000001B _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000004DFE74D 0000000020698360 0000000012AB2810 0000000020698280 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
0000000004E136AD 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
0000000004BEBCEB 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000004EDA970 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
0000000004E5F88A 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors

Application: kicad
Version: (5.1.0-546-g924a5e68f), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

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

Tags:

Revision history for this message

eelik (eelik) wrote on 2019-05-13:

#1

Yet another one. I was creating and editing a pin, got warning about incompatible grid when clicking OK, canceled it, hit Esc a couple of times and clicked canvas with LMB. Drmingw info is similar, addresses are a bit different.

Revision history for this message

eelik (eelik) wrote on 2019-05-13:

#2

Again. This time the last action was clicking RMB on an empty location on the canvas.

kicad.exe caused an Access Violation at location 0000000004B71AC2 in module _eeschema.kiface Reading from location 0000000000000008.

AddrPC Params
0000000004B71AC2 0000000004EE19E0 0000000004EE37D0 0000000012A61FF0 _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000004BD8083 0000043D0000053A 000007FEFD5910C8 000000000000001B _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000004DEE74D 0000000021AD82D0 0000000021AD8348 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
0000000004E036AD 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
0000000004BDBCEB 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000004ECA970 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
0000000004E4F88A 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors

Revision history for this message

eelik (eelik) wrote on 2019-05-13:

#3

And again... I just opened a symbol and clicked on canvas.

Now I have to do real work and change to a stable version.

Michael Kavanagh (michaelkavanagh) on 2019-05-13

Changed in kicad:
importance:	Undecided → Critical
milestone:	none → 6.0.0-rc1
tags:	added: eeschema

Revision history for this message

eelik (eelik) wrote on 2019-05-13:

#4

Crash on another machine, this time Windows 10. I just did some random clicking after starting the symbol editor and and selecting a symbol. Drmingw output is the same:

kicad.exe caused an Access Violation at location 0000000006111AC2 in module _eeschema.kiface Reading from location 0000000000000008.

AddrPC Params
0000000006111AC2 00000000064819E0 000000001557F620 0000000016844190 _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000006178083 FFFFFF060000011C 00007FFD052E9D0C 00000000168441F8 _eeschema.kiface!SCH_IO_MGR::FindPlugin
000000000638E74D 00000000168442D0 0000000016844348 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
00000000063A36AD 0000000000000000 00000000168442D0 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
000000000617BCEB 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!SCH_IO_MGR::FindPlugin
000000000646A970 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
00000000063EF88A 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors

Application: kicad
Version: (5.1.0-546-g924a5e68f), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

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

Revision history for this message

eelik (eelik) wrote on 2019-05-13:

#5

I think I found a simple way to repeat at least one situation.

Open the symbol editor from the project window so that eeschema isn't open. Click RMB on the empty canvas. It crashes every time with the same drmingw output.

Revision history for this message

eelik (eelik) wrote on 2019-05-13:

#6

I just noticed that Michael Kavanagh also reported the last one. I'll test the fix later if it happens to prevent other crashes, too.

Michael Kavanagh (michaelkavanagh) on 2019-05-13

Changed in kicad:
status:	New → Incomplete

Revision history for this message

Michael Kavanagh (michaelkavanagh) wrote on 2019-05-22:

#7

@eelik any update? Can this be closed?

Revision history for this message

eelik (eelik) wrote on 2019-05-22:

#8

I've been waiting if I have need for a new symbol. Usually crashes happen when doing real work, not when just testing... I suppose this can wait a bit longer?

Michael Kavanagh (michaelkavanagh) on 2019-05-22

Changed in kicad:
milestone:	6.0.0-rc1 → none

Revision history for this message

eelik (eelik) wrote on 2019-05-23:

#9

Unfortunately it still happens. The message from drmingw isn't identical but similar. I created a symbol, copied and pasted content from another symbol and then selected and tried to move that content.

kicad.exe caused an Access Violation at location 0000000005E47011 in module _eeschema.kiface Reading from location 0000000000000047.

AddrPC Params
0000000005E47011 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!KIFACE_1
0000000005F51B56 000000002AC68210 0000000000000000 0000000000000000 _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000005F62EA7 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!SCH_IO_MGR::FindPlugin
0000000006244C80 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors
00000000061C96CA 0000000000000000 0000000000000000 0000000000000000 _eeschema.kiface!FOOTPRINT_LIST::DisplayErrors

Revision history for this message

eelik (eelik) wrote on 2019-05-23:

#10

Again, this time I just tried to move ref or val items of a newly created symbol. The access violation message is now identical to the latest one above execpt addresses.

Revision history for this message

eelik (eelik) wrote on 2019-05-23:

#11

Sorry, forgot to add version info for 2 latest comments...

Application: KiCad
Version: (5.1.0-637-gaee1fe45f), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

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

Revision history for this message

eelik (eelik) wrote on 2019-06-03:

#12

I have now tested on Win7 and Win10 and the symbol editor doesn't crash anymore.

Michael Kavanagh (michaelkavanagh) on 2019-06-03

Changed in kicad:
milestone:	none → 6.0.0-rc1
status:	Incomplete → Fix Committed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.