crash after looking at pad property in footprint editor

Bug #1660276 reported by Nicholas Savenlid
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Critical
Maciej Suminski

Bug Description

Opening properties on a pin works fine, closing the property dialog gives a crash.

files attached

Application: kicad
Version: (2017-01-29 revision 75ffcbc)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.51.0 OpenSSL/1.0.2j zlib/1.2.8 libssh2/1.8.0 nghttp2/1.16.1 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.62.0
Curl: 7.51.0
KiCad - Compiler: GCC 6.3.0 with C++ ABI 1010
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  KICAD_SCRIPTING_ACTION_MENU=OFF
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_SCH_IO_MANAGER=OFF
                  KICAD_USE_OCE=ON

Tags: gal
Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :
Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

the footprint file

description: updated
Changed in kicad:
status: New → Confirmed
Revision history for this message
jean-pierre charras (jp-charras) wrote :

Some comments (Windows Build):
It happens only in GAL mode.
Editing a pad from the board editor does not create this issue.
This issue is reproducible when importing a footprint from the footprint editor.

When Kicad is built in debug mode, the crash is immediate when trying to edit a pad in the fp editor, whenever the footprint.
gdb crashes when trying to get the backtrace.

Changed in kicad:
importance: Undecided → Critical
tags: added: gal
Revision history for this message
Maciej Suminski (orsonmmz) wrote :

It is one of the strangest bugs I have ever seen. As far as I can tell, the most reliable way to reproduce it is to change a pad width to make it ~2x bigger than its length and apply the change. Happens only with Windows, so we are left with crappy debugging tools. Bisecting..

Changed in kicad:
assignee: nobody → Maciej Sumiński (orsonmmz)
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 6561c8e61a59fdfa2fab3de89ab828a968be67dc
https://git.launchpad.net/kicad/patch/?id=6561c8e61a59fdfa2fab3de89ab828a968be67dc

Changed in kicad:
status: Confirmed → Fix Committed
Jeff Young (jeyjey)
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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