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
3.0 SC crashes at disconnect after running EXECUTE STATEMENT as non-current user [CORE4705] #5013
Comments
Modified by: @pavel-zotovAttachment: firebird_log_and_trace_when_fbt_run_against_core_2729.zip [ 12682 ] |
Modified by: @pavel-zotovsummary: 3.0 SC: crash when running fbt_run with ES EDS => 3.0 SC: crash when running fbt_run with ES |
Commented by: @pavel-zotov One more note: NO crash when running similar script via ISQL, it seems that problem somehow related to fbt_run.exe If I run the following batch: @echo off ::--------------------------- test SuperClassic ---------------------- set fbc=C:\MIX\firebird\fb30sc ::--------------------------- test SuperServer ----------------------- set fbc=C:\MIX\firebird\fb30 del %fdb% 2>nul And script for it: set term ^ ;
end -- then no crash, but in firebird.log the following lines will appear: CSPROG Fri Mar 06 22:40:22 2015 CSPROG Fri Mar 06 22:40:22 2015 |
Modified by: @pavel-zotovdescription: WI-T6.3.0.31698, SuperClassic only. When running: fbt_run -b <FB30_SC_home> bugs.core_2729 -o localhost/<port> -- FB crashes, see attached firebird.log. File "bugs.core_2729.fbt" contains following test_script section:
""" PS. Windows error message appears ONCE if trace is not running and FIVE times when trace has been launched before fbt_run for this test. PPS.
|
Commented by: @dyemanov Please re-test with a fresh build, please. |
Commented by: @pavel-zotov WI-T3.0.0.31702, SuperClassic. Now there is *no* crash of FB service. === CSPROG Sat Mar 07 11:17:36 2015
|
Modified by: @pavel-zotovAttachment: fb30sc-log-for-build-31702.zip [ 12683 ] |
Commented by: @dyemanov While these issues may both be related to the "linger" feature, I'd rather separate them. If the crash is gone, this ticket should be closed. |
Modified by: @dyemanovVersion: 3.0 Beta 1 [ 10332 ] Fix Version: 3.0 Beta 2 [ 10586 ] Component: Engine [ 10000 ] summary: 3.0 SC: crash when running fbt_run with ES => 3.0 SC crashes at disconnect after running EXECUTE STATEMENT as non-current user |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] assignee: Dmitry Yemanov [ dimitr ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Cannot be tested Test Details: Issue related to fbt_run itself. No error occured when run test script ISQL. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @pavel-zotov
Attachments:
firebird_log_and_trace_when_fbt_run_against_core_2729.zip
fb30sc-log-for-build-31702.zip
WI-T6.3.0.31698, SuperClassic only.
When running:
fbt_run -b <FB30_SC_home> bugs.core_2729 -o localhost/<port>
-- FB crashes, see attached firebird.log.
File "bugs.core_2729.fbt" contains following test_script section:
"""
execute block returns (
user_on_start varchar(32),
user_on_extds varchar(32),
same_attach char(1)
) as
declare v_att_ini int;
declare v_att_eds int;
begin
"""
-- please see it in SVN: qa/fbt-repository/trunk/tests/bugs/core_2729.fbt
PS. Windows error message appears ONCE if trace is not running and FIVE times when trace has been launched before fbt_run for this test.
PPS.
firebird.conf:
DefaultDbCachePages = 256
LockHashSlots = 22111
TempCacheLimit = 256M
MaxUnflushedWrites = -1
MaxUnflushedWriteTime = -1
SharedCache = false
SharedDatabase = true
RemoteServicePort=3330
ExternalFileAccess = Restrict C:\MIX\firebird
TempDirectories = c:\temp
MaxUserTraceLogSize = 99999
FileSystemCacheThreshold = 65536K
AuthServer = Legacy_Auth,Srp
AuthClient = Legacy_Auth,Srp,Win_Sspi
WireCrypt = Disabled
UserManager = Legacy_UserManager
BugcheckAbort = 1
Commits: d2db1a7 FirebirdSQL/fbt-repository@8fb0015
====== Test Details ======
Issue related to fbt_run itself. No error occured when run test script ISQL.
The text was updated successfully, but these errors were encountered: