PCBNew and EESHEMA crash when started

Bug #1851381 reported by Andrew Edwards
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Unknown

Bug Description

Setting up a new laptop. Installed KiCad, it ran fine for a few days. Suddenly I couldn't open anything in EESHEMA or PCBNEW without it crashing immediately. The EESCHEMA or PCBNEW window will open, toolbars are present but the canvas stays white and the program locks up.
I found I could get it to launch if I deleted everything in my appdata folder.
Tracked it to both the eeshema and pcbnew files in appdata.
Tracked it further to the values for SchematicFramePos_x and SchematicFramePos_y in eeschema and PcbFramePos_x and PcbFramePos_y in pcbnew.
Turns out, when I use my external monitor, drag my eeshema or pcbnew windows over to my external monitor (Both screens are 1080p, set to extend in windows display settings, external monitor is monitor 2, located to the right of my main monitor), then close kicad, these values get updated to the following:
SchematicFramePos_x=1912
SchematicFramePos_y=-8
The next time I try to launch the application, it crashes. If I change the 1912 value to -8, the window opens on my primary monitor and I have no problem.
When trying to replicate on a colleagues machine, they get a framPos_x of 2391 and they have no problem opening and closing the program. i.e. I cannot replicate this on another machine. It is EXTREMELY consistent on my new laptop.

Application: KiCad
Version: (5.1.4)-1, release build
Libraries:
    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 8 (build 9200), 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:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Revision history for this message
Andrew Edwards (aedwardskraken) wrote :

Laptop is running Windws 10 Home Version 1809
i7-9750H
16GB of RAM
512GB M2 SSD
RTX 2070

Revision history for this message
Seth Hillbrand (sethh) wrote :

If you change the y position to 0, does it crash?

Changed in kicad:
status: New → Incomplete
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2580

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

Other bug subscribers

Remote bug watches

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