Currently, there exists a leak related to equeuing data. This was discovered after spamming requests to the async server using the sync client (with the memory leak happening in the client spamming messages). The memory usage does not show under a process on task manager, however the total usage percent does increase.
This issue report is actually incorrect and can be attributed to my incorrect usage when testing. I oversaturated the send queue too quickly in a completely unrealistic usecase.
Currently, there exists a leak related to equeuing data. This was discovered after spamming requests to the async server using the sync client (with the memory leak happening in the client spamming messages). The memory usage does not show under a process on task manager, however the total usage percent does increase.