KiCad.exe Crashes When Project is moved to a diff folder

[Andrey Kuznetsov]

To reproduce:
Create New Project called "x", go to project folder, create new folder called "x", cut all files created by KiCAD and paste them into the new "x" folder. At this point KiCAD will crash. Was able to reproduce this 4 times.

Using:
Application: kicad
Version: 4.0.2-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), 64-bit edition, 64 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

I got a crash notice:
Problem signature:
  Problem Event Name: APPCRASH
  Application Name: kicad.exe
  Application Version: 0.0.0.0
  Application Timestamp: 00505f00
  Fault Module Name: wxbase30u_gcc_custom.dll
  Fault Module Version: 3.0.2.0
  Fault Module Timestamp: 00000000
  Exception Code: c0000005
  Exception Offset: 000000000015fe75
  OS Version: 6.3.9600.2.0.0.256.48
  Locale ID: 1033
  Additional Information 1: 2efd
  Additional Information 2: 2efdf02b72bd1ff3bf334b4ff4ffb647
  Additional Information 3: 3c2e
  Additional Information 4: 3c2e1821985020c4603416117c1f9ca2

[xzcvczx (xzcvczx)]

can't reproduce on osx 4.0.2 or latest nightlies

[Novak Tamas (novak-7)]

Can't reproduce on Win7 as well.

- I've opened KiCad launcher, loaded project then opened both eeschema and pcb_new.

- While all 3 open, I moved all KiCad file from project folder to a subfolder.

Left File pane of KiCad launcher immediately changed according to its files "disappear", but eeschema and pcb_new have kept working. Programs have handled the situation even when I clicked Save: a new project.kicad_pcb file created in empty project folder (original projet.kicad_pcb remained intact in subfolder)

So how did you make it happen? step-by-step please

[Andrey Kuznetsov (kandrey89)]

Right, so just tested it and it's tricky.
There seems to be a dependence on the location you're saving to. If the disk is local, then it's fine, but if it's a samba mount on windows, then it's a problem.
Also, I can't reproduce it using Explorer, perhaps because it's too slow or does a move command differently. I am using Total Commander, and it crashes KiCad whenever I move the new project files.
It does not work if I delete the files, or if I copy, wait then delete.
It does not matter which project file you move, .pro, .sch, .kicad_pcb, all trigger the crash. I tried 1 file instead of all files at the same time, and 1 file also crashed KiCad.
Somehow the act of moving the files, triggers a crash, and from the looks of the module name it's in wxbase.

Again, the steps:
open KiCad 4.0.2 stable
create new project and save it to a samba share
go to that location with Total Commander
move all the created KiCad project files to a different folder (anywhere), but it must be a total commander move command (F6) or a ctrl+x and ctrl+v
KiCad.exe crashes as soon as the files are gone from the directory

If you think this is too obfuscated in the sense that I have to use this third party program and do it this way and do it on a samba share and no one is ever going to do it that way, so why fix it. Well, I've done it this way, and who knows how else this bug presents, it's a bug, it should be fixed.

[xzcvczx (xzcvczx)]

there has been a redo of the file watcher stuff that i believe is in the tree for 4.0.3 (and is in nightlies) probably not worth working on until it has been verified if that is still an issue there

[Novak Tamas (novak-7)]

I can't reproduce it. I don't know if 6936 is after file watcher remake, but my config

Work: Win7/x64 6936 nightly.
Remote: Win8.1/x64, Windows share
TotalCommander 8.52a/x64 running on Work.

Project created into Remote share folder, files remotely moved to another folder by Commander...
files disappearded in Kicad launcher's project list immediately, as expected without crash.

[Andrey Kuznetsov (kandrey89)]

Tried 6990 build, still crashes.
I also noticed that it doesn't happen if you move from share to local disk, it only seems to happen when moved from share to share, like when moving into an existing subfolder of where the project was created.
Maybe it's timing related somehow. My remote share is on the same network swing, median pings 1ms and max up to 200ms.

Application: kicad
Version: (2016-07-20 BZR 6990, Git 78e4787)-product, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.46.0 OpenSSL/1.0.2d zlib/1.2.8 libidn/1.32 libssh2/1.6.0 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.59.0
Curl: 7.46.0
KiCad - Compiler: GCC 5.2.0 with C++ ABI 1009
        Settings: 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

[jean-pierre charras (jp-charras)]

Is it really reasonable to move the project you are currently working on?

[Andrey Kuznetsov (kandrey89)]

It's not unreasonable to expect a program not to crash on you, whatever you do!

[xzcvczx (xzcvczx)]

if you want this more likely to be fixed in some decent time frame then you will need to provide a backtrace as you are using a very odd workflow that is unlikely for any developers to have the a similar setup and that file manager.

[Novak Tamas (novak-7)]

I wouldn't set to "Confirmed Low" until noone can reproduce the issue...and I can't: I moved files from \\Media\c\temp\kicad to \\Media\c\temp\kicad\save and yet nothing wrong.

For me it's strange to have max ping time of 200msec on a LAN. Can that be the problem?
I have a small LAN on gigabit switch and ping is always 1msec. If your box may go to a little "nap" for 200msec, it may cause trouble.

Please provide Simon the backtrace data.

[Launchpad Janitor (janitor)]

[Expired for KiCad because there has been no activity for 60 days.]