Footprint editor: all footprint libraries are empty

[Wayne Stambaugh]

Periodically when I open the footprint library editor the progress dialog flashes quickly and all of the footprint libraries are empty (pressing the expand tree node button does nothing). Closing kicad and deleting the fp-info-cache file resolves the issue. I've only noticed this on windows. Perhaps there should be a flag to force a reload the first time the fp-lib-table is loaded after kicad is run regardless of the fp-info-cache state.

Application: kicad
Version: (6.0.0-rc1-dev-1218-g240051fb2), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.62.0 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.7 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.62.0
    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

[Jeff Young (jeyjey)]

For now I've put in code which invalidates the cache if the fp-info-cache file was empty. This should cause it to be re-generated only in the error condition. Let me know if you still see issues....

[KiCad Janitor (kicad-janitor)]

Fixed in revision c0168619629986ef947bd8731b51c100b4c86589
https://git.launchpad.net/kicad/patch/?id=c0168619629986ef947bd8731b51c100b4c86589

[Wayne Stambaugh (stambaughw)]

@Jeff, I just got bit by this again on 6.0.0-rc1-dev-1237-g9514a527c so it doesn't look like your fix solved the problem. I've attached the fp-info-cache file that is currently causing this issue in hopes that it might help.

[Jeff Young (jeyjey)]

Wow, is that cache ever messed up. (But it's not empty, so no, my earlier patch wouldn't have helped any.)

Given the way fields aren't where they're supposed to be, I'm guessing this is a line-ending issue (which would also explain why it's only showing up on one platform). I'll merge another patch to escape/unescape them.