Fix yamux stream destructor (Closes #240) #335
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.
Overview
This PR implements the yamux stream destructor improvements as requested in issue #240. The changes ensure that YamuxStream objects are properly cleaned up immediately when destroyed, preventing potential
CONNECTION_TOO_MANY_STREAMSerrors.Problem
The original implementation had several issues:
CONNECTION_TOO_MANY_STREAMSerrors when many streams were createdSolution
Key Changes
Modified YamuxedConnection to use weak_ptr
Streamstype fromstd::unordered_map<StreamId, std::shared_ptr<YamuxStream>>tostd::unordered_map<StreamId, std::weak_ptr<YamuxStream>>PendingStreamsmap to hold strong references until handlers are invokedImplemented proper ~YamuxStream() destructor
doClose(Error::STREAM_CLOSED_BY_HOST)Removed cleanup timer mechanism
setTimerCleanup()method and related timer logicAdded pending_streams_ map
Files Modified
include/libp2p/muxer/yamux/yamuxed_connection.hppsrc/muxer/yamux/yamuxed_connection.cppinclude/libp2p/muxer/yamux/yamux_stream.hppsrc/muxer/yamux/yamux_stream.cppTesting
all_muxers_acceptance_testhost_integration_testmuxers_and_streams_testBenefits
Closes #240