Fatal crash eeSchema V5 assigning footprint

[Brian Piccioni]

Application: kicad
Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build 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=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON

When editing a specific component (resistor) to assign a footprint, if I browse footprints, select R_1206 handsoldering and double click or select "Insert Footprint in board" the footprint browser would crash and throw error "Error unmapping vertices buffer:invalid operation".

After this, the browser would hang and all KiCad windows would no longer function until all were killed via Task Manager.

This happened eveyr time I tried it until I decided to use CVPCB to assign the footprint. After that the error was thrown once then disappeared and even new parts would not cause a problem.

This was a file imported from V4 if that matters.

[Maciej Suminski (orsonmmz)]

Is it specific to a component/footprint/schematic? If you used nightlies for a longer period of time, do you know when the problem appeared?

[Brian Piccioni (br0an)]

This was my first ever use of a nightly. I have only worked on one schematic but witnessed it with several parts. The problem went away after CVPCB but then came back later. I will be working on other schematics and will try and keep better track of what happens and when.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Maciej Suminski
Sent: February 7, 2018 4:01 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

Is it specific to a component/footprint/schematic? If you used nightlies for a longer period of time, do you know when the problem appeared?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I tried it until I decided to use CVPCB to
  assign the footprint. After that the error was thrown once then
  disappeared and even new parts would not cause a problem.

  This was a file imported from V4 if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1747546/+subscriptions

[Brian Piccioni (br0an)]

Confirmed on second schematic: Added R_SMALL tried to assign via library browser. Picker R_1206_handsoldering Kicad crapped out. See screen capture. Kicad closed itself and I had to reload. Tried again but this time a capacitor. Different message, but failure. Had to close all Kicad windows via Task Manager (Kicad non-responsive)

This was also a schematic imported from V4

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Maciej Suminski
Sent: February 7, 2018 4:01 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

Is it specific to a component/footprint/schematic? If you used nightlies for a longer period of time, do you know when the problem appeared?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I tried it until I decided to use CVPCB to
  assign the footprint. After that the error was thrown once then
  disappeared and even new parts would not cause a problem.

  This was a file imported from V4 if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1747546/+subscriptions

[Maciej Suminski (orsonmmz)]

Does pcbnew work well for you when running in modern/OpenGL mode? Could you try opening a board design, 3D viewer and footprint editor at the same time?

Also, what is your video card?

[Brian Piccioni (br0an)]

Attached, please find my complete system info file from Windows.

The system has Intel HD graphics 530 and Nvidia GTX960M. I have permanently switched to Modern Accelerated. I have never used 3D viewer. Should I?

When I have had issues it was from eeschema (PCBNew not opened). I just tried with PCBNew opened and when I edit the component in eeschema, click through the library browser, double click to select the component (i.e. a 16 pin header), the error gets flagged and Kicad dies and has to be closed from the Task Manager.

I have a small project where this is completely reproducible.

What can I do to help?

This morning I downloaded the latest nightly.

Application: kicad
Version: (2018-02-08 revision be70ce7d4)-makepkg, release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build 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=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Maciej Suminski
Sent: February 8, 2018 10:10 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

Does pcbnew work well for you when running in modern/OpenGL mode? Could you try opening a board design, 3D viewer and footprint editor at the same time?

Also, what is your video card?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I...

[Maciej Suminski (orsonmmz)]

I wanted you to open 3D viewer to see if there are problems with multiple OpenGL windows opened. Could you try it? For now I do not have an explanation regarding what is going on, unfortunately. As far as I understand, you did not have such problems with KiCad 4.x?

[Brian Piccioni (br0an)]

I see. I tried the 3D viewer and had no crash related issues on the board I am working with at the moment. This is a small board and I ran CVPCB on it and it didn't crash after that.

I am going to be doing a number of little boards so I'll try that if /when I have another issue. I am pretty sure that when I had the first problem I wasn't even running PCBNew, just eeSchema and the footprint browser. So the next time I get a crash, I'll try loading PCBNew, then the 3D viewer and see what changes.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Maciej Suminski
Sent: February 9, 2018 8:52 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

I wanted you to open 3D viewer to see if there are problems with multiple OpenGL windows opened. Could you try it? For now I do not have an explanation regarding what is going on, unfortunately. As far as I understand, you did not have such problems with KiCad 4.x?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I tried it until I decided to use CVPCB to
  assign the footprint. After that the error was thrown once then
  disappeared and even new parts would not cause a problem.

  This was a file imported from V4 if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1747546/+subscriptions

[Brian Piccioni (br0an)]

Oh, and no I had no such problem with KiCad 4. Most of these boards were designed under Kicad 4 and I have decided to change the approach and figured I'd try the nightlies to make sure my RenuKiCadPCB utility didn't choke in case of change in file format or something.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Maciej Suminski
Sent: February 9, 2018 8:52 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

I wanted you to open 3D viewer to see if there are problems with multiple OpenGL windows opened. Could you try it? For now I do not have an explanation regarding what is going on, unfortunately. As far as I understand, you did not have such problems with KiCad 4.x?

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I tried it until I decided to use CVPCB to
  assign the footprint. After that the error was thrown once then
  disappeared and even new parts would not cause a problem.

  This was a file imported from V4 if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1747546/+subscriptions

[Maciej Suminski (orsonmmz)]

Brian,

Since you managed to build KiCad, could you try to run a debug build with gdb attached and get the backtrace? It would be very helpful, as I have no means to reproduce the problem, even though I have tried a few different OS/hardware sets.

[Brian Piccioni (br0an)]

Maciej

I don't know how to do what you describe. Usually when I have debugged I have run inside Eclipse and have no idea how to do that with a program such as Kicad.

If you describe the step's I'll give it a try, assuming, of course, the bug shows up as it did when I reported it.

Brian

-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of Maciej Suminski
Sent: March 22, 2018 6:49 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

Brian,

Since you managed to build KiCad, could you try to run a debug build with gdb attached and get the backtrace? It would be very helpful, as I have no means to reproduce the problem, even though I have tried a few different OS/hardware sets.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I tried it until I decided to use CVPCB to
  assign the footprint. After that the error was thrown once then
  disappeared and even new parts would not cause a problem.

  This was a file imported from V4 if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1747546/+subscriptions

[Maciej Suminski (orsonmmz)]

If you managed to reproduce the problem reliably and now it stops, then I will be even happier to hear that.

I assume you have followed "Building using MSYS2" paragraph in the official documentation. If so, you will need to create another subdirectory in the source directory and rerun the cmake line replacing "-DCMAKE_BUILD_TYPE=Release" with "-DCMAKE_BUILD_TYPE=Debug", followed by the usual make and make install commands. You will also need to install gdb itself ('pacman -S mingw-w64-x86_64-gdb' command in the msys2 shell).

Once it is done, you will get a KiCad build with debug symbols. The next step is to run KiCad with gdb (simply launch 'gdb kicad' in the msys2 shell). In the gdb command prompt you need to execute 'run' command to actually start KiCad. Once you manage to crash it, type 'bt' in the gdb shell and post it here.

Many thanks for your cooperation, please let me know if any of the instructions is not clear.

1. http://docs.kicad-pcb.org/doxygen/md_Documentation_development_compiling.html

[Brian Piccioni (br0an)]

OK. I'll see if I can reproduce the problem. I have been side-tracked from using Kicad working on the build process (now fixed), and studying the source to see if I can offer my own code for geographically renumbering PCB reference designations and back-annotating.

It may take a while to get back to you.

Brian

-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of Maciej Suminski
Sent: March 22, 2018 11:15 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

If you managed to reproduce the problem reliably and now it stops, then I will be even happier to hear that.

I assume you have followed "Building using MSYS2" paragraph in the official documentation. If so, you will need to create another subdirectory in the source directory and rerun the cmake line replacing "-DCMAKE_BUILD_TYPE=Release" with "-DCMAKE_BUILD_TYPE=Debug", followed by the usual make and make install commands. You will also need to install gdb itself ('pacman -S mingw-w64-x86_64-gdb' command in the
msys2 shell).

Once it is done, you will get a KiCad build with debug symbols. The next step is to run KiCad with gdb (simply launch 'gdb kicad' in the msys2 shell). In the gdb command prompt you need to execute 'run' command to actually start KiCad. Once you manage to crash it, type 'bt' in the gdb shell and post it here.

Many thanks for your cooperation, please let me know if any of the instructions is not clear.

1. http://docs.kicad-
pcb.org/doxygen/md_Documentation_development_compiling.html

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I tried it until I decided to use CVPCB to
  assign the footprint. After that the error was thrown once then
  disappeared and even new parts would not cause a problem.

  This was a file imported from V4 if that matters.

...

[Brian Piccioni (br0an)]

One thing - and sorry for the stupid questions, I am mainly used to developing microcontroller related stuff so its hard for me to even figure where to look for the answers.

In my build/release directory I end up with a bunch of exe's, etc., install of an install file or something along those lines. When I manually copy those into the kicad tree it works but there is a rick I'm leaving something behind, which would muddy the water.

Is there a script or something which either produces the installer, a zip file, or something along those lines?

By the way, GDB was installed and I started the debug build.

Brian

-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of Maciej Suminski
Sent: March 22, 2018 11:15 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

If you managed to reproduce the problem reliably and now it stops, then I will be even happier to hear that.

I assume you have followed "Building using MSYS2" paragraph in the official documentation. If so, you will need to create another subdirectory in the source directory and rerun the cmake line replacing "-DCMAKE_BUILD_TYPE=Release" with "-DCMAKE_BUILD_TYPE=Debug", followed by the usual make and make install commands. You will also need to install gdb itself ('pacman -S mingw-w64-x86_64-gdb' command in the
msys2 shell).

Once it is done, you will get a KiCad build with debug symbols. The next step is to run KiCad with gdb (simply launch 'gdb kicad' in the msys2 shell). In the gdb command prompt you need to execute 'run' command to actually start KiCad. Once you manage to crash it, type 'bt' in the gdb shell and post it here.

Many thanks for your cooperation, please let me know if any of the instructions is not clear.

1. http://docs.kicad-
pcb.org/doxygen/md_Documentation_development_compiling.html

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  lo...

[Peter R. Schaefer (prs0203)]

I am running KiCad under max os and have the same problem.
With the nightly build March 20 all is ok. with the nightly build March 22 I get the crash when I wish to assign a footprint.

[Maciej Suminski (orsonmmz)]

Peter, Brian, could you check if it has anything to do with the footprint libraries setup? Could you try to clear the library table and see if KiCad will crash? If not, add some libraries and continue until it crashes. This way we can pinpoint the faulty files and analyze them, in case it is a footprint matter.

Brian, we do not have scripts for KiCad packaging stored in the source repository. I am not really familiar with the packaging process, but I may reach the people who know if needed. You should be fine with copying just *.kiface files and corresponding *.exe files. It should be enough to run 'make install' and then invoke the applications from the msys2 shell afterwards.

[Maciej Suminski (orsonmmz)]

Peter, what is the exact KiCad version you are running? We fixed one issue that lead to crash when one tried to assign a footprint to a symbol that had none or an invalid footprint assigned before. You may simply test the next nightly, it is very likely the problem is fixed already.

[Jon Evans (craftyjon)]

@Brian:

1) you probably want to do a debug build to get a good backtrace with gdb for the crash

2) if you run `make install` with a msys2 build, it installs it to your msys2/mingw64/bin directory. The Windows installer that you download from the website is created separately, I am not actually sure how to do that but you typically wouldn't do that as part of a debug build.

@Peter, this is probably not the same issue as Brian's original report, could you please open a new bug report and include more details about how you saw the crash (i.e. does it happen anytime you try to assign a footprint, or just sometimes? can you place footprints in pcbnew? etc)

[Maciej Suminski (orsonmmz)]

I suspect Peter's issue has been fixed in e1c8822, so perhaps there is no need for a detailed bug report. It all depends on which version he is using now.

[Brian Piccioni (br0an)]

Maciej

I made a debug build and ran it using debug as you suggested. Unfortunately, as of this build I cannot replicate the bug. The good news is I now know what to do if it appears again. It was absolutely consistent in the past.

Brian

Application: kicad
Version: (5.0.0-rc2-dev-269-gff3f22987), debug build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.57.0 OpenSSL/1.0.2n (WinSSL) zlib/1.2.11 libidn2/2.0.4 libssh2/1.8.0 nghttp2/1.29.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.66.0
    Curl: 7.57.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build 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_OCE=ON
    KICAD_SPICE=ON

-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of Maciej Suminski
Sent: March 22, 2018 11:15 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

If you managed to reproduce the problem reliably and now it stops, then I will be even happier to hear that.

I assume you have followed "Building using MSYS2" paragraph in the official documentation. If so, you will need to create another subdirectory in the source directory and rerun the cmake line replacing "-DCMAKE_BUILD_TYPE=Release" with "-DCMAKE_BUILD_TYPE=Debug", followed by the usual make and make install commands. You will also need to install gdb itself ('pacman -S mingw-w64-x86_64-gdb' command in the
msys2 shell).

Once it is done, you will get a KiCad build with debug symbols. The next step is to run KiCad with gdb (simply launch 'gdb kicad' in the msys2 shell). In the gdb command prompt you need to execute 'run' command to actually start KiCad. Once you manage to crash it, type 'bt' in the gdb shell and post it here.

Many thanks for your cooperation, please let me know if any of the instructions is not clear.

1. http://docs.kicad-
pcb.org/doxygen/md_Documentation_development_compiling.html

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
  Build Info:
      wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
      Boost: 1.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.0 with C++ ABI 1011

  Build 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=ON
      BUILD_GITHUB_PLUGIN=ON
      KICAD_USE_OCE=ON
      KICAD_SPICE=ON

  When editing a specific component (resist...

[Maciej Suminski (orsonmmz)]

Actually, it is great news! Thank you for your assistance Brian, we really appreciate it. I am closing the report, as it used to be easily reproducible while it is no longer the case.

[Brian Piccioni (br0an)]

I keep getting a bounceback but

Thanks for that! In my experience with a bug the worse case situation is when it just disappears.

Still - glad to be of help. Like I said, I now can build so I can test more intelligently.

Brian

[Maciej Suminski (orsonmmz)]

There have been some changes to the footprint selector code recently, so I suppose it is not like the bug disappeared on its own. Perhaps the faulty code has been modified/removed, at least that is what I hope.

[Peter R. Schaefer (prs0203)]

Sorry for my late response. I was busy...
With the nightly build

kicad-20180323-043044.29ebca4-c4osx

is working fine.

Peter