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

Review of exception raising and handling in memory manager [CORE1242] #1666

Open
firebird-automations opened this issue May 3, 2007 · 3 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Relate to CORE1240

Current exception handling in memory manager needs re-evaluation to make it more robust. There is a potential for severe bugs when something wrong happens on object destruction (bad release order etc.).

"We can't (at least on MacOS PPC platform) throw exceptions from memory pool, when it's mutex is locked! Compiler needs some memory to create exception, it calls new for this - and in that new that same mutex is attempted to be entered once more."

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue relate to CORE1240 [ CORE1240 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1 Alpha 1 [ 10150 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 12003 ] => Firebird [ 15559 ]

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

No branches or pull requests

1 participant