Crash after placing one symbol and saving

[Gordon Hardman]

I am using the latest nightly (April 8), Win 10 64 bit pro. I open my project and so long as I do not place a symbol it seems fine. I can change from page to page, cut and paste, generate a netlist etc. But here are the steps that seem to reliably crash it:

1. Start Kicad
2. Open root .sch
3. Shift-A to go to place symbol tool
4. Place "+10V" power symbol from my library
5. Ctrl-S to save- Kicad crashes with "Microsoft Visual C++ Runtime Library" message that kicad.exe has requested the Runtime to terminate in an unusual way.

I think it has been doing this for a few nightlies now. But the whole project was created on this machine and moved from 4 to 5, and all seemed well until this.

I verified the steps above 4 times, just to be sure. Tried with various symbols, same result.

Acer PC, Celeron processor, 2GHz, 8GB RAM. Intel HD graphics.

[Maciej Suminski (orsonmmz)]

Could you check what are the factors leading to a crash? Does the issue occur with any schematic file, any symbol from your library or simply any (power) symbol? If the problem is observable only with your files, would you share them so we can try to recreate the problem?

[Nick Østergaard (nickoe)]

Please add complete version info.

[Gordon Hardman (radio-gordon)]

Application: kicad
Version: (5.0.0-rc2-dev-395-gcb2c447c2), 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
    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=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON

[Maciej Suminski (orsonmmz)]

Gordon,

Could you check what are the factors leading to a crash? Does the issue occur with any schematic file, any symbol from your library or simply any (power) symbol? If the problem is observable only with your files, would you share them so we can try to recreate the problem?

[Wayne Stambaugh (stambaughw)]

I cannot reproduce this in either normal or stand alone mode with both 32 and 64 bit versions of kicad on windows 10. Please attach the schematic or a sample project if you cannot post your schematic that exhibits the problem to this bug report.

[Gordon Hardman (radio-gordon)]

On travel for a while- I will try to get to this soon.

On 4/13/2018 14:42, Wayne Stambaugh wrote:
> I cannot reproduce this in either normal or stand alone mode with both
> 32 and 64 bit versions of kicad on windows 10. Please attach the
> schematic or a sample project if you cannot post your schematic that
> exhibits the problem to this bug report.
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[Maciej Suminski (orsonmmz)]

Hi Gordon,

Any chance you have managed to gather more data for the report?

[Gordon Hardman (radio-gordon)]

I have been updating to the latest nightly release every day. I have been busy routing a big project with no problems. I have now gone back to my "test" project, and I cannot replicate this problem using the steps I outlined, although the problem was initially totally repeatable.
At this point I have some critical project deadlines, and I am nervous to go back and experiment!

[Maciej Suminski (orsonmmz)]

Alright, thank you for the heartening message. Good luck with your project!

[Wayne Stambaugh (stambaughw)]

Can the status of this bug report be set to fix committed since the original project no longer exhibits the problem or cannot be duplicated by anyone else? @Gordon, do you have the footprint viewer enabled in the symbol chooser dialog? If so, that may have been the issue which was recently fix. I don't want to release rc2 with known crash bugs.

[Maciej Suminski (orsonmmz)]

Setting to 'Fix committed' as the bug is not reproducible anymore.