Interactive HTML BOM plugin - cannot launch after opening Footprint Editor window

Just noticed with current 6.0rc nightly that I can’t open Interactive HTML BOM plugin after I open Footprint editor from within the PCB editor.
If I close my PCB and reopen it without opening the Footprint editor, all seem OK.
@qu1ck do you think it’s something with the Plugin itself, or Kicad? With previous install (yesterday build) all I got after trying to launch IBOM was KiCad totally crashing (not longer reproducible with current nightly).

Crash was discussed in https://gitlab.com/kicad/code/kicad/-/issues/9798
Probably FP editor thing is also related or has common cause. I don’t think it’s because of the plugin. Does scripting console work with/without opening FP editor?

Dragons ahead.
So far managed to crash KiCad by launching IBOM, by launching scripting console and got KiCad to display some error loop in Kicad’s wxPython stdout/stderr console.

I get something like that under Windbg

ModLoad: 00007ffd11800000 00007ffd11836000 C:\WINDOWS\system32\xmllite.dll
(1634.3b00): C++ EH exception - code e06d7363 (first chance)
ModLoad: 00007ffce9b20000 00007ffce9bc9000 C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
(1634.3b00): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
_grid!PyInit__grid+0x18925:
00007ffcda4bc7d5 48ff6058 jmp qword ptr [rax+58h] ds:0000000000000058=???

One more thing.
Except for the random crashes I do get, the scripting console in general is not dependant on the FP editor launched or not. While the IBOM certaintly is.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.