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

Races in cch, leading to AV during cache_writer startup [CORE1098] #1519

Closed
firebird-automations opened this issue Jan 18, 2007 · 13 comments
Closed

Races in cch, leading to AV during cache_writer startup [CORE1098] #1519

firebird-automations opened this issue Jan 18, 2007 · 13 comments
Assignees
@AlexPeshkoff
Labels
affect-version: 2.0.0 affect-version: 2.0.1 component: engine fix-version: 2.1 Alpha 1 priority: major qa: cannot be tested type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

When shutting down database, it may be closed by shutdown thread before complete initialization of cache_writer() thread. It leads to dbb becoming wrong (illegal pointer) in cache_writer() and therefore SS fails immediately after database shutdown is complete.

Commits: a13e291 48e12a6 5aad7a4 5da8116
@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

Fix Version: 2.1 [ 10041 ]

Fix Version: 2.0.1 [ 10090 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Added special flag in BCB to control cache_writer startup.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

It looks like v1.5.x should also be affected. Isn't it so?

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Seems to be so. Do you suggest to backport fix?

If yes, the most useful would be to move tag 2.0.1 first - why release version with known AV?
What about 1.5.4, I'm afraid it's too late for it.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

I mostly meant the "Affects Versions" field of the ticket :-)

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

I've mentioned versions where I've reproduced a bug. I did not test for 1.5.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11511 ] => Firebird [ 15499 ]

@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.0.0 affect-version: 2.0.1 component: engine fix-version: 2.1 Alpha 1 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