3D view crash Pcbnew

Bug #1829800 reported by Hildo Guillardi Júnior on 2019-05-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Jon Evans

Bug Description

3D view freeze Pcbnew to crash. This bug appeared one day after some update to the Raytracing that made it calculate from the center.

Application: Pcbnew
Version: 6.0.0-unknown-f21face~86~ubuntu16.04.1, release build
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.15.0-50-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:

Jon Evans (craftyjon) wrote :

Can you say more about what you were doing when you get the crash?

Sure. I just went to View>>3D Viewer of a board that I am layouting (it reproducible with any board and in 2 Linux-Ubuntu-PCs).

Follow the information about the segment fault.

gdb pcbnew
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from pcbnew...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/pcbnew
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeace1700 (LWP 9121)]
[New Thread 0x7fffea4e0700 (LWP 9122)]
[New Thread 0x7fffe9cdf700 (LWP 9123)]
[New Thread 0x7fffcad1d700 (LWP 9141)]
[New Thread 0x7fffca51c700 (LWP 9142)]
[Thread 0x7fffcad1d700 (LWP 9141) exited]
[Thread 0x7fffca51c700 (LWP 9142) exited]
[New Thread 0x7fffca51c700 (LWP 9143)]
[New Thread 0x7fffcad1d700 (LWP 9144)]
[Thread 0x7fffca51c700 (LWP 9143) exited]
[New Thread 0x7fffca51c700 (LWP 9148)]
[New Thread 0x7fffc91aa700 (LWP 9149)]
[Thread 0x7fffca51c700 (LWP 9148) exited]
[Thread 0x7fffc91aa700 (LWP 9149) exited]
[New Thread 0x7fffc91aa700 (LWP 9150)]
[New Thread 0x7fffca51c700 (LWP 9151)]
[Thread 0x7fffca51c700 (LWP 9151) exited]
[Thread 0x7fffc91aa700 (LWP 9150) exited]
[New Thread 0x7fffc91aa700 (LWP 9152)]
[New Thread 0x7fffca51c700 (LWP 9153)]
[Thread 0x7fffc91aa700 (LWP 9152) exited]
[Thread 0x7fffca51c700 (LWP 9153) exited]
[New Thread 0x7fffca51c700 (LWP 9154)]
[New Thread 0x7fffc91aa700 (LWP 9155)]
[Thread 0x7fffca51c700 (LWP 9154) exited]
[Thread 0x7fffc91aa700 (LWP 9155) exited]

Thread 1 "pcbnew" received signal SIGSEGV, Segmentation fault.
0x00007ffff7b9abd0 in wxAuiToolBarItemArray::DoEmpty() ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_aui-3.0.so.0
(gdb) trace
Tracepoint 1 at 0x7ffff7b9abd0
(gdb) trace
Note: breakpoint 1 also set at pc 0x7ffff7b9abd0.
Tracepoint 2 at 0x7ffff7b9abd0

Jon Evans (craftyjon) wrote :

OK, I think this is fixed in 20800d03b792e47b12f642e9bf448640603d7d46

Changed in kicad:
status: New → Fix Committed
importance: Undecided → Critical
milestone: none → 6.0.0-rc1
assignee: nobody → Jon Evans (craftyjon)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers