[5.0.2] PCBNew Assert failed when open Design rules window

Bug #1821450 reported by Michal on 2019-03-23

This bug report was marked for expiration 0 days ago. (find out why)

This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

After attempting to open Design rules window, PCBnew Assert failed with the following info:
../wxWidgets-3.0.4/src/generic/grid.cpp(1307):assert"(row >= 0 && row < GetNumberRows()) && (col>=0 && col<GetNumberCols())" failed in SetValue(): invalid row or column index in wxGridStringTable
Do you want to stop the program?
You can choose [Cancel] to suppress futher warnings.

This happened several times, and then I could normally open my Desgin rules window.

Seth Hillbrand (sethh) wrote :

Thank you for the report. Please note that 5.0.2 will not be receiving updates at this time. Please download and test the 5.1 release. If this behavior continues (which it should not), we'll be able to address it.

Changed in kicad:
status: New → Incomplete
Michal (mikon) wrote :

Just to include more information: KiCad 5.0.2 running on Win7/64.
Unfortunately this happened multiple times, then things went normal. Probably some data structures have been being built in the back.
Will update to 5.1.0 just after the initial dust will fall down -- running on production environment so not very "early adopter".

Nick Østergaard (nickoe) wrote :

Please add proper version info

Michal (mikon) wrote :

Application: kicad
Version: (5.0.2)-1, release build
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:

Wayne Stambaugh (stambaughw) wrote :

Since the design rules dialog was completely rewritten, I suspect this bug has already been released.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers