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
AST in given environment is actually signal handler. It can happen at any moment, therefore possible activities in AST are very limited. One of the rules is that there should be no new/delete operators during AST processing. But database snapshot AST is using class ClumpletWriter, which may perform memory allocation when clumplets are added to it. corrupting therefore dbb_permanent memory pool.
I do not have direct confirmations that it happens, but do have 2 core files, where dbb_permanent is corrupted, and it's known that people who got that cre files were actively working with monitoring tables.
Submitted by: @AlexPeshkoff
AST in given environment is actually signal handler. It can happen at any moment, therefore possible activities in AST are very limited. One of the rules is that there should be no new/delete operators during AST processing. But database snapshot AST is using class ClumpletWriter, which may perform memory allocation when clumplets are added to it. corrupting therefore dbb_permanent memory pool.
I do not have direct confirmations that it happens, but do have 2 core files, where dbb_permanent is corrupted, and it's known that people who got that cre files were actively working with monitoring tables.
Commits: 22011ce 49ee25d
The text was updated successfully, but these errors were encountered: