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
Unfortunately it's a release build, and there's not much info. I have tried reproducing and haven't been able to catch it, so it seems non-deterministic?
Looks like we just need to re-land ce012c0. I wasn't able to reproduce the crash, but I was able to catch a UAF with ASAN. With the above patch re-added, the UAF is gone.
… refs (#7102)".
This was originally added to avoid a use-after-free. However, it got
removed as part of f4920aa. It seems this is still required, even when
we process PathTrackers sequentially. I confirmed there was a
use-after-free without this change, which is fixed after adding this
back.
Closes#7327.
… refs (#7102)". (#7328)
This was originally added to avoid a use-after-free. However, it got
removed as part of f4920aa. It seems this is still required, even when
we process PathTrackers sequentially. I confirmed there was a
use-after-free without this change, which is fixed after adding this
back.
Closes#7327.
I just observed this in an internal design:
Unfortunately it's a release build, and there's not much info. I have tried reproducing and haven't been able to catch it, so it seems non-deterministic?
Perhaps this is related to ce012c0?
That specific code was removed when this was made sequential: f4920aa. But maybe the loop to pre-allocate namespaces is required still?
The text was updated successfully, but these errors were encountered: