V5.1.5 EEschema crashes after new instllation on Win7

Software
1

Very similar to my old topic here (it is still the same computer)

I have serveral version of KiCAD installed in this computer, I ran them all using the KICAD_CONFIG_HOME environment variable and all coexist nicely, today I tried to install v5.1.5 and it crashed the very first time it try to open a project (same as last time), however, trying to create a new project, also crashes EESchema (PCBNew opens a new Project, but crashed on me the very first time I wanted to open an old project -v5.1.4- )

If I copy the “eeschema” file from my previous intallation (5.1.4) into the new installation (5.1.5) it opens without a hitch, something is going on at the time of creation of the file that makes it hang.

Version info:

Application: KiCad
Version: (5.1.5)-2, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.66.0 OpenSSL/1.1.1d (Schannel) zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.39.2
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.71.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.66.0
    Compiler: GCC 9.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

And some error message that I don’t believe would be very useful:

Problemsignatur:
  Problemereignisname:	APPCRASH
  Anwendungsname:	kicad.exe
  Anwendungsversion:	0.0.0.0
  Anwendungszeitstempel:	00000000
  Fehlermodulname:	atio6axx.dll
  Fehlermodulversion:	6.14.10.8787
  Fehlermodulzeitstempel:	4a8a1300
  Ausnahmecode:	c000041d
  Ausnahmeoffset:	00000000006488c4
  Betriebsystemversion:	6.1.7601.2.1.0.256.48
  Gebietsschema-ID:	1031
  Zusatzinformation 1:	1f46
  Zusatzinformation 2:	1f467fb5d7f4a4a5a86e04e85ca044d4
  Zusatzinformation 3:	5e1b
  Zusatzinformation 4:	5e1ba02fafc5925ad61e7201d7c77b2a

Lesen Sie unsere Datenschutzbestimmungen online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfĂĽgbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
  C:\Windows\system32\de-DE\erofflps.txt

Beschreibung:
  Aufgrund eines Problems kann dieses Programm nicht mehr mit Windows kommunizieren.

Problemsignatur:
  Problemereignisname:	AppHangB1
  Anwendungsname:	kicad.exe
  Anwendungsversion:	0.0.0.0
  Anwendungszeitstempel:	00000000
  Absturzsignatur:	a3e1
  Absturztyp:	0
  Betriebsystemversion:	6.1.7601.2.1.0.256.48
  Gebietsschema-ID:	1031
  Zusätzliche Absturzsignatur 1:	a3e1d2496f8c0cc5e792ca09f227b587
  Zusätzliche Absturzsignatur 2:	c242
  Zusätzliche Absturzsignatur 3:	c242f2df4e640a10366d38e92674750b
  Zusätzliche Absturzsignatur 4:	a3e1
  Zusätzliche Absturzsignatur 5:	a3e1d2496f8c0cc5e792ca09f227b587
  Zusätzliche Absturzsignatur 6:	c242
  Zusätzliche Absturzsignatur 7:	c242f2df4e640a10366d38e92674750b

Lesen Sie unsere Datenschutzbestimmungen online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfĂĽgbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
  C:\Windows\system32\de-DE\erofflps.txt

EDIT: Filed a bug report and found a workaround
https://bugs.launchpad.net/kicad/+bug/1854593 [Deprecated]

GitLab bug report:
https://gitlab.com/kicad/code/kicad/issues/2620

1 Like
2

Well, apparently @Seth_h did it again and fixed it, thanks Seth :slight_smile: so, it all should be good in v5.1.6.

1 Like
3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.