[BUG]Vsomeip-3.5.1 Client UDP Port Closed, Server Still Sending Events

[FishPickBeans]

vSomeip Version

v3.5.1

Boost Version

1.84

Environment

Linux

Describe the bug

Linux use Vsomeip-3.5.1 code, Steps:
Firstly, client subscribe server's event-group successed.（vsomip_server.json noly support UDP）
Secondly, client reboot, But server still sending client's sub event.

Reproduction Steps

Linux use Vsomeip-3.5.1 code, Steps:
Firstly, client subscribe server's event-group successed.（vsomip_server.json noly support UDP）
Secondly, client reboot, But server still sending client's sub event.
Thirdly, tcpdump parse by wireshark.

Expected behaviour

after client reboot, server should stop sending before client's sub event.

Logs and Screenshots

vsomeip-3.5.1 log.txt

[FishPickBeans]

Uploading tcpdump_20241014200558.zip…

[duartenfonseca]

Uploading tcpdump_20241014200558.zip…

@FishPickBeans cannot open the tcpdump

[FishPickBeans]

1. The above is the tcpdump released by Vsomeip 3.5.1, but we have already removed tcpdump and are only releasing images now!
2. 172.168.2.30 is the server-side, 172.168.2.80 is the client-side, UDP transmission!
3. The image shows that the server sends an Event with a two second cycle, but the client process has been killed and there is no 1-second interval to SUB!

We speculate that after the client was killed, the server did not clear the client's last SUB information, resulting in continuous sending of events!

Sorry, we chose vsomeip3.4.10 and this issue did not occur!
thank you!