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
Memory in a long-running server was continually growing because when an error occurred the node was saved in an Exception which was saved in a logging event which was stored in the logging event history. The references to the nodes meant that old manifests could not be garbage collected.
We should change Exceptions in logging events to strings, and add 'event_buffer_size' to UserConfig.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Memory growth: stop saving Exceptions in logging events
[CT-1191] Memory growth: stop saving Exceptions in logging events
Sep 15, 2022
Memory in a long-running server was continually growing because when an error occurred the node was saved in an Exception which was saved in a logging event which was stored in the logging event history. The references to the nodes meant that old manifests could not be garbage collected.
We should change Exceptions in logging events to strings, and add 'event_buffer_size' to UserConfig.
The text was updated successfully, but these errors were encountered: