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'm not sure how to reproduce this, but this out of bounds access may be related to the fix that was put in for this issue? #4445 8865c2a
Maybe this caused the out of bounds access
bruth
added
accepted
The defect or proposal as been accepted
bug
Confirmed reproducible bug
and removed
defect
Suspected defect such as a bug or regression
labels
Sep 13, 2023
… hold lock. (#4530)
This unprotected access allowed the cache to most likely be flushed and
after a subsequent writeMsgRecord would have the offset > slot value
which can't happen if lock is held due to us loading cache properly at
beginning of the function.
Signed-off-by: Derek Collison <derek@nats.io>
Resolves#4529
… hold lock. (#4531)
Cherry picked from main.
Fix for a call into mb.recalculateFirstForSubj() from
fs.recalculateFirstForSubj() that did not lock the mb properly.
Signed-off-by: Derek Collison <derek@nats.io>
Resolves#4529
What version were you using?
v2.9.22
What environment was the server running in?
Kubernetes/Linux
Is this defect reproducible?
I'm not sure how to reproduce this, but this out of bounds access may be related to the fix that was put in for this issue? #4445
8865c2a
Maybe this caused the out of bounds access
Given the capability you are leveraging, describe your expectation?
N/A
Given the expectation, what is the defect you are observing?
The server panicked
The text was updated successfully, but these errors were encountered: