PCBNew slow when EEschema open

When PCB new is open, often encounter not able or very slow edtit PCBNew.
I notice that when EESchema is open. When closing EESchema the issues is gone.

Also often encounter “please wait” message from Ubuntu as well now, specially when running a DRC in PCBnew or running a 3D of the design, When closing EESchema the DRC runs faster but PCBNew opens Eeschema upon every DRC run.

When running Kicakd v6 on Ubuntu 22.04 did not experience such issues. It started after moving from Ubuntu 22.04 to 23.04 and Kicad from v6 to v7 at the same time, so hard to say if it’s either one of these.

This is an old PC with NVIDIA grpahics (GF116) but without the native NVIDIA drivers (thus Nouveau), as NVIDIA did not release stable kernel drivers for Linux Kernel 6 and up. Did also notice that running 3D using Wayland is slower than X.org.

Does anyone experience the same issues ?

Try disabling cross-probing. The underlying library for the drawing canvas had an issue where it would slow down due to too many drawing events, but that should be fixed at the next release of the library (but we aren’t quite sure when that will be).

I have noticed that PCBNew (since V7) is very slow (Windows 10). Sometimes I have to wait few seconds until the track to my cursor position is shown. But together with moving to V7 I connected second monitor and since than I work with schematic continuously open at this second screen.
I didn’t thought that having schematic open can be the reason so didn’t checked it.
I supposed that the reason may be that circular tracks are now possible (I didn’t used them) and may be it added some work to be done while routing.

Having a quick look in preferences could not find this cross-probing option

Project manager > Preferences > Schematic Editor > Display Options

You need to un-tick cross-probing in both Schematic and PCB Display Options to turn it off and conversely, tick both to turn on.

These are my settings, Now have all cross probing option unchecked, will see how it goes. But this is a very nice feature took quickly look up components which now cannot be used.

1 Like

The underlying cause of the slowness should be fixed in the next library release by the upstream developers (it is a library called wxWidgets), so you should be able to renable the cross-probing feature once you get that update.

1 Like

Thanks, I use the GTK kit mostly. Does that have to do with Wayland because X.org seems a bit faster as well but that could be due to my old graphics card. (X.org now seems to crash more often since Canonical shifted to Wayland, so X.org it’s not an option the long term)

The code that is slow is the Wayland window drawing code (it is drawing the canvas items even when the window is hidden), so you will see the slowdown when you use Wayland and not Xorg right now. Upstream wx seems to be targetting a fall release for the new library version that will have the fix, but then I am not sure when it will make its way into Ubuntu.

Hello,
I’m experiencing the same problem. Since last release (7.0.6) KiCAD is very laggy (e.g. assigning footprints takes a few seconds for every click).
Disabling cross-probing didn’t solve the problem for me. But it seems to be a problem with EEschema, since PCBNew works OK as long as EEschema is closed.

Application: KiCad x86_64 on x86_64
Version: 7.0.6-7.0.6~ubuntu22.04.1, release build
Libraries:
    wxWidgets 3.2.1
    FreeType 2.11.1
    HarfBuzz 6.0.0
    FontConfig 2.13.1
    libcurl/7.81.0 OpenSSL/3.0.2 zlib/1.2.11 brotli/1.0.9 zstd/1.4.8 libidn2/2.3.2 libpsl/0.21.0 (+libidn2/2.3.2) libssh/0.9.6/openssl/zlib nghttp2/1.43.0 librtmp/2.3 OpenLDAP/2.5.15
Platform: Ubuntu 22.04.3 LTS, 64 bit, Little endian, wxGTK, gnome, wayland
Build Info:
    Date: Jul 7 2023 02:32:39
    wxWidgets: 3.2.1 (wchar_t,wx containers) GTK+ 3.24
    Boost: 1.74.0
    OCC: 7.5.2
    Curl: 7.88.1
    ngspice: 38
    Compiler: GCC 11.3.0 with C++ ABI 1016
Build settings:
    KICAD_SPICE=ON

what video card do you have? what drivers are selected?

Graphics:
  Device-1: AMD driver: amdgpu v: kernel
  Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
    compositor: gnome-shell v: 42.9 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu resolution:
    1: 2560x1440~60Hz 2: 2560x1440~60Hz
  OpenGL: renderer: AMD Radeon RX 6650 XT (navi23 LLVM 15.0.7 DRM 3.49
  6.2.0-26-generic)
    v: 4.6 Mesa 23.3~git2308080600.475527~oibaf~j (git-4755276 2023-08-08
    jammy-oibaf-ppa)

try updating via ppa with switching to closed source drivers

Can you be a bit more specific?

The problem is likely due to wayland/wxWidgets interactions, probably has nothing to do with video card.

If you have to keep using wayland, your options are to wait for a new wx release or to build wx and KiCad from source (see Fix `wxGLCanvas` performance when using Wayland by vadz · Pull Request #23554 · wxWidgets/wxWidgets · GitHub )

2 Likes

https://www.amd.com/en/support/linux-drivers

this is exactly the difference between closed and open source and different drivers…

No, it has nothing to do with drivers.

in the case of nvidi, this helps somewhat