Fix: Reuse PairedTransmitter outside loop to prevent repeated ZMQ socket creation (#268)

[GaneshPatil7517]

@pradeeban

Problem

PairedTransmitter was being created and destroyed inside every loop iteration in 0mq/funcall.py.
This caused excessive ZMQ socket churn, thread creation overhead, and potential port rebinding failures due to TIME_WAIT state.

Solution

• Moved transmitter initialization and background thread start outside the loop
• Added try/finally to ensure proper cleanup after loop execution

Impact

• Improved performance
• Prevents socket exhaustion
• Proper resource lifecycle management
• No functional behavior change

(#268)

[Copilot]

Pull request overview

This PR improves the resource lifecycle in the 0mq/funcall.py ZMQ client loop by reusing a single PairedTransmitter instance instead of creating/tearing it down every iteration, avoiding repeated socket/thread churn.

Changes:

• Instantiate PairedTransmitter once before the simulation loop.
• Start background sync once and stop it once using a try/finally to guarantee cleanup.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.