[dotnet] [bidi] Reuse memory when receiving websocket messages #15640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
User description
🔗 Related Issues
💥 What does this PR do?
Improve memory allocation.
🔧 Implementation Notes
💡 Additional Considerations
🔄 Types of changes
PR Type
Enhancement, Bug fix
Description
Reused a shared
MemoryStream
to optimize memory allocation.Updated
ReceiveAsync
to use the shared memory stream.Improved semaphore handling in
SendAsync
for better performance.Added proper disposal of shared resources in
Dispose
method.Changes walkthrough 📝
WebSocketTransport.cs
Optimize memory and resource management in WebSocketTransport
dotnet/src/webdriver/BiDi/Communication/Transport/WebSocketTransport.cs
MemoryStream
for memory reuse.ReceiveAsync
to use the shared memory stream.SendAsync
.Dispose
.