wxwidgets crash in 5.0.0

Bug #1783037 reported by David Pearce
60
This bug affects 11 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Undecided
Unassigned

Bug Description

Windows 10 64 bit clean install of new 5.0.0

Open pcbnew
Select Tools
The box attached pops up and KiCad freezes. Closing from the error box works.

Application: kicad
Version: (5.0.0), 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
    OpenCASCADE Community Edition: 6.8.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=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Revision history for this message
David Pearce (halzia) wrote :
Revision history for this message
Mark Roszko (mark-roszko) wrote :

Confirming the Windows package was compiled/packaged incorrectly.

Changed in kicad:
status: New → Confirmed
Revision history for this message
David Pearce (halzia) wrote :

This seems to not actually be a crash. The error dialog has grabbed focus and then hides behind the pcbnew window, making it unresponsive.
A work round is to minimise the pcbnew window and select cancel in the error box. This seems to work and then Tools seems to work

tags: added: packaging windows
Revision history for this message
Nick Østergaard (nickoe) wrote :

What installer did you use, the 64 or 32 bit version?

Revision history for this message
David Pearce (halzia) wrote :

The x86_64 bit from the main server on the Windows download page
http://downloads.kicad-pcb.org/windows/stable/kicad-5.0.0-x86_64.exe

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

It is fixed in commit 30da1a3b (5.0 branch).

Revision history for this message
Chris Elliott (sembazuru) wrote :

Is the build option "KICAD_SCRIPTING_ACTION_MENU=OFF" the issue here, or should I open a new bug report to complain about that not being set to "ON" to be able to use action plugins from the menu?

Revision history for this message
Ido Gendel (igendel) wrote :

Hello,

KiCAD 5.0.0 Release Build, Windows 10, 64-bit install
"About" form says:
  wxWidgets: 3.0.3 Unicode and Boost 1.60.0
  Platform: Windows 8 (build 9200)

I have the same issue with Pcbnew, whenever I select/highlight the "Tools" menu item. I can close the error dialog box and continue using the other parts of the program (as far as I checked), but can't access the "Tools" menu no matter what.

Sincerely,

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

I think it is easily reproducible on all Windows installations, we need to recreate the installer to contain KiCad build in release mode.

Revision history for this message
Chris Elliott (sembazuru) wrote :

I found a package that appears to have the 30da1a3b applied. The KICAD_SCRIPTING_ACTION_MENU build option is ON. I don't get a wxwidgets crash when accessing the Tools menu in PCBNew, and all the action scripts that I have installed in "%APPDATA%\kicad\scripting".

Quick note for the peanut gallery. For the RC2-dev and RC3-dev nightlies I had my action script folders installed in "%APPDATA%\kicad\scripting\plugin". With the patched package that I found the Tools menu wouldn't list my plugins until I moved the actions script folders out of the plugin folder to %APPDATA%\kicad\scripting.

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Windows installer has just been updated, please try it out.

Changed in kicad:
status: Confirmed → Fix Committed
Revision history for this message
Ido Gendel (igendel) wrote :

With the updated installer I don't see the error messages I did before.

However, I did not clean my system from the previous installation, where I already chose the option to "suppress further warnings". So I can't tell for sure whether it's actually the new installation that solved the problem or some settings that were saved. Sorry, I'm just a simple user :-)

Thanks for the effort!

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

"Suppress further warnings" is valid only for a single session, so if you restarted KiCad and do not see the assert windows anymore, then it is all fine.

Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.