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
{{ message }}
This repository has been archived by the owner on Jul 31, 2023. It is now read-only.
We should not keep an unbounded number of spans in the active set in spanStore. If a user starts a span without ending it, this will cause a memory leak.
Yes, this is working around potential bugs in user code. But we have actually seen this in the wild (in the Datastore custom spans) and the only reason this didn't cause crashes is that the zpages are not automatically imported. Anyone importing zpages would see a memory leak.
The text was updated successfully, but these errors were encountered:
We should not keep an unbounded number of spans in the active set in spanStore. If a user starts a span without ending it, this will cause a memory leak.
Yes, this is working around potential bugs in user code. But we have actually seen this in the wild (in the Datastore custom spans) and the only reason this didn't cause crashes is that the zpages are not automatically imported. Anyone importing zpages would see a memory leak.
The text was updated successfully, but these errors were encountered: