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.

Sign up for GitHub

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 when already destroyed callback interface is used #8429

Open
AlexPeshkoff opened this issue Feb 3, 2025 · 0 comments
Open

Segfault when already destroyed callback interface is used #8429

AlexPeshkoff opened this issue Feb 3, 2025 · 0 comments
Assignees
@AlexPeshkoff
Labels
affect-version: 4.0.5 affect-version: 5.0.1 affect-version: 6.0 Initial fix-version: 5.0.2 fix-version: 6.0 Alpha 1 type: bug

Comments

@AlexPeshkoff
Copy link
Member

Segfault may be reproduced with multiple levels of EXECUTE STATEMENT calls with ExtConnPoolSize != 0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexPeshkoff AlexPeshkoff

Labels
affect-version: 4.0.5 affect-version: 5.0.1 affect-version: 6.0 Initial fix-version: 5.0.2 fix-version: 6.0 Alpha 1 type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlexPeshkoff