LinuxCNC 2.8.1 configuration doesn't run after upgrading from 2.7.15

It looks like HAL is limited to 348160 bytes:
github.com/LinuxCNC/linuxcnc/blob/master.../hal/hal_priv.h#L333

That does allow for a few thousand HAL pins, but perhaps that isn't always enough?

(I have checked, and ulimit -l is no help)

2052 Pins ! " quand on aime on ne compte pas ! "
my component gearboxmikron is in userspace it
does not influence, but if I remove an rt component, I gain pins in the xml (last hal loaded)

this is under 2.7.15 RTAI with max locked memory : 20480

Just an idea ...
Are all your pyvcp components in custom_gvcp.hal? That's why I had very confusing reports.

Is your 2.8.1 configuration running on the same OS and machine as the 2.7.15 configuration?

It is possible that the HAL pins take up more space on a 64-bit OS than on a 32-bit OS.

There is certainly no reason to expect any difference in behaviour here between 2.7.15 and 2.8.1 caused by LinuxCNC changes alone.

chris@cnc wrote: Just an idea ...
Are all your pyvcp components in custom_gvcp.hal? That's why I had very confusing reports.

hello chris,
You can organize your configuration with multiple successive hal files, you just have to declare
them in the [hal] section of the ini boot file. Exemple base.hal, custom.hal, test.hal etc
At the very end you have a last hal file which is read after the GUI (axis for exemple) is loaded.
it loads the hal connections with the Pyvcp interface add-in which is designed with the xml file

andypugh wrote: Is your 2.8.1 configuration running on the same OS and machine as the 2.7.15 configuration?

It is possible that the HAL pins take up more space on a 64-bit OS than on a 32-bit OS.

There is certainly no reason to expect any difference in behaviour here between 2.7.15 and 2.8.1 caused by LinuxCNC changes alone.

No,
2.7.15 Debian Wheezy is under i386 so in 32 bit because with RTAI
2.8.1 Debian 10 buster therefore under 64 bit with Prempt-RT
the 2 OS runs on the same hardware, each on an SSD hard drive