-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check failed: static_cast<int64_t>(u_.json_obj.cons.bytes_used) >= size #4725
Comments
@romange it's important + urgent. We trigger a check failed in json so something could be off with our mem tracking |
I see here a test and a bug. What should I understand from this? :) |
Because check fails are hard crashes and can cause service disruption and I would like this fixed on the next version. I suspect we have a bug around memory tracking and I would like to avoid crashes in production |
If you still think it's not that important I am happy to remove the labels |
every crash bug is important but we estimate urgency based on empirical evidence whether this bug does really affect anything. |
gotcha, removing it then |
fixes dragonflydb#4725 Signed-off-by: Stepan Bagritsevich <[email protected]>
fixes dragonflydb#4725 Signed-off-by: Stepan Bagritsevich <[email protected]>
fixes dragonflydb#4725 Signed-off-by: Stepan Bagritsevich <[email protected]>
fixes dragonflydb#4725 Signed-off-by: Stepan Bagritsevich <[email protected]>
How to reproduce:
The text was updated successfully, but these errors were encountered: