Footprint editor fails to read footprints from library

[Dave Vandenbout]

I have an fp-lib-table with 1,087 entries for libraries which are all stored locally. When I first open the footprint editor, there is a 20-second delay as all the libraries are scanned. After that, I can open footprints from individual libraries with no problem.

After *closing and then re-opening* the main KiCad application, re-opening the footprint editor does the following:
 1) There is no delay for scanning the 1,087 libraries. The progress indicator appears and disappears quickly.
 2) All the libraries appear in the left-hand pane, but clicking on the "+" by a library name causes it to change to a "-" while failing to show the individual footprints within that library (i.e. the footprints do not appear below the library name as a drop-down list).

This problem persists even after re-installing the KiCad application.

I can make the problem disappear by reducing my fp-lib-table file to 116 or fewer libraries. Any more than that and the problem returns.

I can also make the problem disappear for the entire list of 1,087 libraries if I include at least one library that is fetched from Github instead of locally. That seems to cause the footprint editor to scan the entire list of libraries (which takes about 20 seconds).

Application: KiCad
Version: (5.1.4)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
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.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    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

[Rene Poeschl (poeschlr)]

This might have something to do with the fp-lib-cache as it parses footprints the first time round. As a test try to delete that file (found in your project directory) and see if this triggers the parser to start again.

[Dave Vandenbout (devb)]

Yes, removing the fp-info-cache file from the project directory fixes the problem with the footprint editor.

[Wayne Stambaugh (stambaughw)]

I've seen this as well but I have yet to determine what triggers it. It only seems to affect MSW.

[Jeff Young (jeyjey)]

Hi Dave,

Just one clarification: fixes permanently, or do you have to delete it every time you run Kicad?

Thanks,
Jeff.

[Dave Vandenbout (devb)]

I have to delete fp-info-cache before starting KiCad or else the footprint editor problem occurs. However, I can run the footprint editor multiple times without error within the *same* KiCad session even though the fp-info-cache file appears after the first run of the footprint editor.

[Wayne Stambaugh (stambaughw)]

@Jeff, I just manage to trigger this performing the following steps:

1) Open project in KiCad 5.1.4.
2) Launch the footprint library editor (fp-info-cache dialog increments as expected).
3) Library tree expands as expected.
4) Close KiCad 5.1.4.
5) Open KiCad master branch.
6) Launch Pcbnew.
7) Attempt to add new footprint to the board.
8) fp-info-cache dialog stalls as shown in attached bitmap and cannot be dismissed.
9) Close footprint chooser dialog.

From this point on the footprint chooser tree cannot be expanded as though no footprints were loaded. I also include the fp-info-cache file. It did not look corrupt to me but I'm not 100% sure what I am looking for. It looks to me like there is some type of thread deadlock that is preventing the fp-info-cache from being loaded correctly.

[KiCad Janitor (kicad-janitor)]

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/1814