-
Notifications
You must be signed in to change notification settings - Fork 598
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
Allow to configure the backtrace tracing for failed allocation #13376
base: main
Are you sure you want to change the base?
Conversation
⚪ |
⚪ |
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
@@ -51,6 +51,8 @@ message TTableServiceConfig { | |||
optional uint64 MaxNonParallelTopStageExecutionLimit = 26 [default = 1]; | |||
optional bool PreferLocalDatacenterExecution = 27 [ default = true ]; | |||
optional uint64 MaxNonParallelDataQueryTasksLimit = 28 [default = 1000]; | |||
|
|||
optional bool VerboseMemoryLimitException = 29 [default = true]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Если это управляется динамически, что мешает управлять этим флагом per-query? Какой-нибудь служебной прагмой.
Changelog entry
Also fix heap-use-after-free for failed allocation backtrace
Changelog category