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
I noticed that there is a similar issue #4900 which has been closed. But I think the core problem has not been resolved. The real reason causes this issues is that the activity (If in my example) is setting result continuously (calling context.Set method) and the ActivityOutputRecord is created continuously at the same time.
In my example code, my workflow won’t exit. So ActivityOutputRegister won’t be disposed, too.
I think that makes sense, because for each activity execution, any of its output is captured. So the question is, what kind of controls should we offer to manage this? For example:
Provide a threshold configuration that will discard older output.
Disable collecting output altogether
Flush output to the underlying store during commit states (which is part of a separate issue).
Description
Program memory will increase continuously when execute a activity with result in a loop.
Steps to Reproduce
Here is my workflow to run.
Actual Behavior
The number of
_records
inActivityOutputRegister
is increasing continuously. The memory is going to be 700M after 15 min.Environment
The text was updated successfully, but these errors were encountered: