pcbnew crashes when placing a via that collides with other nets

[Nicholas Savenlid]

100% reproducible

and that is not very common for being me :-)

1: you have a trace end
2: you click on trace end to resume routing
3: press "v" to get a via
4: via bounces into surrounding traces and shows that it will collide
5: ignore that and place the via anyway
6: crash

picture attached showing what it looks like before step 5

Application: kicad
Version: (2017-09-19 revision dddaa7e69)-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 7 (build 7601, Service Pack 1), 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

[Nicholas Savenlid (nicholas-z)]

and the infamous result attached

[jean-pierre charras (jp-charras)]

I cannot reproduce this crash.
Your Kicad nightly build is a bit old.
Please try a more recent version and see if happens.

[Nicholas Savenlid (nicholas-z)]

crashes rock solid

I will have to make a video to be believed (again)

Application: kicad
Version: (2017-11-14 revision 419c6e198)-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 7 (build 7601, Service Pack 1), 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

[Nicholas Savenlid (nicholas-z)]

ps

all my libraries went down the drain when i upgraded.

removed from project.

My option was to accept all the new kicad libraries or have all my own libraries thrown out and end up with nothing.

odd thing
ds

not a good day today

[Wayne Stambaugh (stambaughw)]

On 11/15/2017 10:15 AM, Nicholas Savenlid wrote:
> ps
>
> all my libraries went down the drain when i upgraded.
>
> removed from project.
>
> My option was to accept all the new kicad libraries or have all my own
> libraries thrown out and end up with nothing.
>
>
> odd thing
> ds

Nothing odd about this at all. It is exactly what was supposed to
happen. Please see http://kicad-pcb.org/post/symbol-lib-table/.

>
> not a good day today
>

[Tomasz Wlostowski (twlostow)]

Nicholas,

I can't reproduce this issue with the latest master. Could you send us the PCB design that shows the problem? A stack trace would also be *extremely* useful.

Tom

[Nicholas Savenlid (nicholas-z)]

yes, i followed the instructions and "all" went well

he missed only one component.

"Warning: No symbol 'LP2992AILD-3.3_NOPB' found in symbol library table."

why it complained i dont know, because it was there in the texas lib, and i could pick it from lib and manually put it back again.

some hundred other components it had no problem with, about 20 libs was used i guess.

sorry for OT

[Nicholas Savenlid (nicholas-z)]

I can send the pcb design over email

its not public domain,

provide email, and i send it.

thanks

2017-11-15 17:09 GMT+01:00 Tomasz Wlostowski <email address hidden>:

> Nicholas,
>
> I can't reproduce this issue with the latest master. Could you send us
> the PCB design that shows the problem? A stack trace would also be
> *extremely* useful.
>
> Tom
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1732376
>
> Title:
> pcbnew crashes when placing a via that collides with other nets
>
> Status in KiCad:
> Incomplete
>
> Bug description:
> 100% reproducible
>
> and that is not very common for being me :-)
>
> 1: you have a trace end
> 2: you click on trace end to resume routing
> 3: press "v" to get a via
> 4: via bounces into surrounding traces and shows that it will collide
> 5: ignore that and place the via anyway
> 6: crash
>
> picture attached showing what it looks like before step 5
>
>
> Application: kicad
> Version: (2017-09-19 revision dddaa7e69)-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 7 (build 7601, Service Pack 1), 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1732376/+subscriptions
>

[Nicholas Savenlid (nicholas-z)]

I offered to send the design via email

not a good option ?

[Maciej Suminski (orsonmmz)]

I contacted Nicholas and he says he cannot reproduce the bug with the current nightly.

[Nick Østergaard (nickoe)]

This bug was introduced only in master and is fixed in master, we consider that fix released then.