Concurrent proxy creation causes abort (core dump) with 3+ simultaneous proxies

[nhuvaoanh123]

Description

When 3 or more proxy instances are created simultaneously for the same service, 1-2 proxies abort with core dump (SIGABRT). This occurs consistently with maxSubscribers: 5 configuration.

Reproduction

1. Start skeleton with maxSubscribers: 5
2. Start 3-5 proxy processes simultaneously (within 1 second)
3. Observe 1-2 proxies crash with Aborted (core dumped)

Environment

• Ubuntu 24.04, Bazel 8.3.0, score-communication v0.1.4 (commit 07e6cf4)
• Custom CAN bridge binary using VehicleSignalSkeleton/Proxy types

Expected Behavior

All proxies should successfully connect and receive data up to maxSubscribers limit.

Actual Behavior

Proxy 1: 10 samples received
Proxy 2: 10 samples received  
Proxy 3: Aborted (core dumped)

Workaround

Stagger proxy startup with 1+ second delay between each.

Analysis

Likely race condition in shared memory region creation or service discovery flag file access during concurrent FindService + Create calls.

Found during Taktflow Systems bench integration testing.