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
Because we have different retry / expiration policies for different cache errors, we are eagerly parsing the CacheError in check_expiry.
Though this code path is used both in main symbolicator, as well as in the cleanup job. Parsing the CacheError variants from the file involves String::from_utf8_lossy, which allocates and can thus OOM the cleanup task.
It is a bit weird though that the cleanup task is using as much memory and OOM-ing, as ideally none of these errors should not be that large ideally.
The text was updated successfully, but these errors were encountered:
Because we have different retry / expiration policies for different cache errors, we are eagerly parsing the
CacheError
incheck_expiry
.Though this code path is used both in main symbolicator, as well as in the
cleanup
job. Parsing theCacheError
variants from the file involvesString::from_utf8_lossy
, which allocates and can thus OOM thecleanup
task.It is a bit weird though that the cleanup task is using as much memory and OOM-ing, as ideally none of these errors should not be that large ideally.
The text was updated successfully, but these errors were encountered: