dwf.Device().open() stalls when called in a multiprocessing subprocess

[felixFleetZero]

Had a software running the latest version of pydwf using multiprocessing with one of the sub-process managing an Analog Discovery 2 USB interface to do analog input measurement on one channel.
The expected behaviour was working then, which is that this sub-process was managing the measurement from that instrument, while others managed measurement from other instruments in parallel.
As the pydwf package is now removed from Github and future support seems discontinued, tried to replace it with dwfpy.

After updating the class that was using pydwf as its low-level interface, it seems to work as expected when used on its own (in a main of a single process).
However, as soon as it's used in its intended multiprocessing subprocess as before, it doesn't show the same behaviour.
The subprocess seems stuck to infinity in the dwf.Device().open() function call.
Note that the start method is "fork".
Running on Python 3.11.2, digilent.waveforms_3.22.2_arm64, and digilent.adept.runtime_2.27.9-arm64 on a raspberry pi 4.

Any insight on why this could be know that nothing else changed apart from transitioning from pydwf to dwfpy?

[mariusgreuel]

As dwfpy is merely a wrapper, my best guess is that it is not related to the dwfpy library but the waveforms library used below. It sound strange when you mention that it worked with a different wrapper. Out of the top of my head, I do not have any ideas what might be wrong.