Windows 10 Pro 32 bit - PrintPreview - Kicad Crash

Software
1

Greetings,

Under 32 bit Win 10 Pro my Eeschema print preview

function causes Kicad to crash. I can print OK but if I try to use
the File>Print>Print Prevue function the whole Kicad session crashes.
I don’t really know if this is a Windows 10 only issue as I did not
install Kicad until after my Win 10 upgrade.

My Windows Kicad version info is:
Version 4.0.0-rc1-stable, release build
wxWidgets 3.0.2 Unicode and Boost 1.57.0
Platform: Windows 8 (build 9200), 32 bit.

I wonder if anybody else has run into this issue?

I wonder if this might be  solved when a Windows 10

build becomes available?

tma

2

Same problem for me with W10 Family edition 32bit and Kicad 4.0.0 rc1.

Application: kicad
Version: 4.0.0-rc1-stable release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC 5.2.0,wx containers,compatible with 2.8)
Platform: Windows 8 (build 9200), 32 bit, Little endian, wxMSW
Boost version: 1.57.0
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=ON
USE_FP_LIB_TABLE=HARD_CODED_ON
BUILD_GITHUB_PLUGIN=ON

Patrick

3

eeschema print preview fine here on windows 10 64 bit

4

Thanks for the info!

Starting to sound like this bug only applies to Windows 32 bit but still not sure if it only applies to Windows 10. I wonder if anyone here can confirm that Eeschema>File>Print>Print Preview works OK under 32 bit Windows 7?

I wonder if this is already a known bug?

5

Can’t help with 32bit…
Installed 4.0.0 RC1 over an older version (BZR5***) on Windows 7 Home Premium 64bit and this:

Eeschema>File>Print>Print Preview

works OK.

6

Yep, same issue I encountered, see here: Bug with new release?
4.0.0RC1 has a bug on the x32 build, building from source works fine, and the latest x32 build works fine, not sure when they fixed it, I did find out but forgot now, was a few weeks, possibly a month ago now. Of course, not sure when the next stable release candidate will be available, it should be fixed in that build, but until such time you will have to use a nightly build to do print preview.