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

Jump to bottom

SegFault in page AST routine under high load [CORE2590] #3000

Closed
firebird-automations opened this issue Aug 13, 2009 · 6 comments
Closed

SegFault in page AST routine under high load [CORE2590] #3000

firebird-automations opened this issue Aug 13, 2009 · 6 comments
Assignees
@AlexPeshkoff
Labels
affect-version: 2.5 Beta 2 component: engine fix-version: 2.5 RC1 priority: major qa: cannot be tested type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Database's lock is released during attach when PIO routines are called. At this time lock is already present, but BCB reamins NULL. In AST no check for dbb_bcb is ready for use is present.

Commits: 4fe226c 289f84d
@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Lock manager kept internally owners with ASTs being delivered, but at the same time made it possible for appropriate objects in engine to be released. Under high load, including multiple attach/detach database, this caused various bugs in superclassic mode.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10362 ]

@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
Assignees

@AlexPeshkoff AlexPeshkoff

Labels
affect-version: 2.5 Beta 2 component: engine fix-version: 2.5 RC1 priority: major qa: cannot be tested type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexPeshkoff @firebird-automations