You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only start the stream monitoring after events are send out
Currently it is almost impossible to capture the full binary stream of a
process even if one adds a listener right after creation of the stream
proxy. The reason is that the streams are immediately started to being
read in the constructor. The code currently uses some caching in place
but this only works reliable for a single listener and is then reset
afterwards having other missing data depending on how fast they can
register. Even worse there is a small chance that after registration and
before reading the buffer some bytes are received and then is processed
before the buffer contents.
This now creates a new constructor that only creates the stream but do
not start them. Instead users must call the method startMonitoring for
this. The RuntimeProcess now uses this constructor to delay the start of
stream reading unless all notifications are performed so other parties
can register accordingly.
0 commit comments