Topic: Repeatable failure with AVB Controller and outgoing streams
I've tried reporting this bug via email directly to the varioous RME support emails I had from previous issues but I'm getting no reply.
IT's been happening ever since I got my RME AVB system around two years ago, but has got worse in recent months to the point where it fails nearly every time I switch my studio on - and I lose 30mins of production time every time.
My system is:
- macOS laptop or desktop
- RME digiface AVB
- RME m1610 pro
- Presonus AVB switch
Steps to reproduce:
1) power switch on and wait a few minutes (or leave it on)
2) power on all AVB equipment.
3) connect RME digiface AVB to laptop or dekstop
4) audio input streams work but no audio output streams work
Codex says
"Codex said:
"Yes—with high confidence, this is a software robustness fault in RME AVB Controller 0.9891 or one of its bundled AVDECC/libpcap components.
What is proven:
- The Controller received `SIGSEGV` while one thread was using a pcap network handle and another was closing the AVDECC network layer.
- Ethernet, discovery and gPTP remained healthy.
- Restarting only the Controller restored the AVB streams.
- A network device appearing or disappearing must not crash the application, regardless of switch timing.
The likely bug is an unsynchronised close/use operation—possibly a use-after-close. `pcap_get_selectable_fd` is where it crashed, but that does not necessarily mean libpcap itself is defective; RME’s code or bundled AVDECC library may have passed it an invalid handle.
The incomplete connection restoration after relaunch appears to be a second robustness problem: the Controller failed to reconcile the desired connection state with the actual network state.
What we cannot yet prove without RME’s symbols/source code is exactly which internal component owns the defect or whether a newer Controller release fixes it. But from a customer/support perspective, this is legitimately an RME Controller software defect. The switch may have supplied the timing trigger; it did not justify or directly cause the process crash."
"
I have a crash log too which may be useful (and I've sent via email)