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?
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.
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?
-- /bugs.launchpad .net/bugs/ 1747546
You received this bug notification because you are subscribed to the bug report.
https:/
Title:
Fatal crash eeSchema V5 assigning footprint
Status in KiCad:
New
Bug description: 7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3 compatible with 2.8)
Application: kicad
Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
Libraries:
wxWidgets 3.0.3
libcurl/
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,
Boost: 1.60.0
Curl: 7.54.1
Compiler: GCC 7.1.0 with C++ ABI 1011
Build settings: WX_GRAPHICS_ CONTEXT= OFF WX_OVERLAY= OFF SCRIPTING= ON SCRIPTING_ MODULES= ON SCRIPTING_ WXPYTHON= ON SCRIPTING_ ACTION_ MENU=ON GITHUB_ PLUGIN= ON USE_OCE= ON SPICE=ON
USE_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_
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: /bugs.launchpad .net/kicad/ +bug/1747546/ +subscriptions
https:/