Hi alt
Following your instructions, I tested the application in more detail. I noticed that the memory usage starts to increase even before calling Sms.ForSubmit() or creating a new instance of DeliverSm().
This increase seems to be related to the call routes, as the footprint increases before any ...
Search found 2 matches
- Tue Nov 18, 2025 3:12 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: SmppClient SubmitSm Memory Leak - Objects Not Released (v2.9.35)
- Replies: 2
- Views: 50
- Mon Nov 17, 2025 3:12 pm
- Forum: Inetlab.SMPP v2.x (.NET Standard, .NET Core)
- Topic: SmppClient SubmitSm Memory Leak - Objects Not Released (v2.9.35)
- Replies: 2
- Views: 50
SmppClient SubmitSm Memory Leak - Objects Not Released (v2.9.35)
Hi everyone,
I've identified a potential memory leak in the Inetlab.SMPP client library
when working with SubmitSm PDU creation.
Issue:
- Creating SubmitSm objects or using SMS.ForSubmit() does not properly release
memory after the objects are disposed or go out of scope.
- Memory profiler ...
I've identified a potential memory leak in the Inetlab.SMPP client library
when working with SubmitSm PDU creation.
Issue:
- Creating SubmitSm objects or using SMS.ForSubmit() does not properly release
memory after the objects are disposed or go out of scope.
- Memory profiler ...