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
Server crash after ubnormal disconnect with open ExecuteStatement [CORE2173] #2604
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff It's wider reproducible. |
Commented by: @AlexPeshkoff sorry - selected in wrong box |
Modified by: @AlexPeshkoff |
Commented by: @AlexPeshkoff If we decide, it's easy to have a fix in 2.0.5. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1.2 [ 10270 ] Fix Version: 2.0.6 [ 10303 ] |
Modified by: @AlexPeshkoff |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: @romansimakov
Relate to CORE2179
Block progress on CORE2183
Test case:
1) Create database.
CREATE TABLE T (I INTEGER);
SET TERM ^ ;
CREATE PROCEDURE P RETURNS (O INTEGER)
AS
begin
for execute statement 'select i from t' into :o do
begin
suspend;
end
end
^
SET TERM ; ^
2) Generate 10000 records by IBExpert for inserting into T. It's for perform not full fetch.
3) Execute 'select * from p' by IBExpert (isql fetch all records and in this case bug is not reproduced)
4) Kill ibexpert.exe process by Tast Manager, since while normal exit it ask to confirm or rallback transaction.
AV occurs in ExecuteStatement::Close in CallbackWrapper since tdbb->tdbb_transaction at this moment is NULL.
Commits: 2ee3645 4f48013
The text was updated successfully, but these errors were encountered: