Warn once at the held-message bound, tell receivers sendResp() is what releases a message, and pin that a refused segment joins no group

2026-09-26 14:41:10 +02:00
parent fb6b125aab
commit b9167073d4
8 changed files with 50 additions and 21 deletions
@@ -405,6 +405,11 @@ and is also what the panel ranked hardest — two methods, one answer.

 ## Worth doing, not blocking

+- [ ] **Make the dumbclient soak's memory sample evidence of no library leak again.** Its rss ends at
+      its maximum (298 MiB, heapUsed 81 MiB after 173,820 messages), which the harness's own per-id
+      `Set` and `answerOrder` explain but cannot separate from a leak in `src/`: sample the heap
+      after the bookkeeping is cleared. From the stability review of #29.
+
 - [ ] **Decide whether `alert_notification` reaches the application as more than `incomingPduObj`.**
      It is the SMSC saying a handset it could not reach is reachable again (`esme_addr`,
      `ms_availability_status`); a client has no `onRequest`, so the raw PDU event is the only way in.