Skip to content
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

Database permanent pool may get corrupted when working with monitoring tables [CORE2483] #2896

Closed
firebird-automations opened this issue May 29, 2009 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => In Progress [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: In Progress [ 3 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1.3 [ 10302 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment