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
Updating blob field cause server crash with ACCESS_VIOLATION exception [CORE3097] #3476
Comments
Commented by: Vorobiev Victor (arxange1) Firebird crash: drWatson's report file |
Modified by: Vorobiev Victor (arxange1)Attachment: drwtsn32.log [ 11696 ] |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.0.7 [ 10390 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred Test Details: Confirmed crash on 2.0.6. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: Deferred => Done successfully Test Details: Confirmed crash on 2.0.6. => Confirmed crash on 2.0.6.
|
Submitted by: Vorobiev Victor (arxange1)
Is related to QA256
Attachments:
drwtsn32.log
Server crashes when we try update blob field with string which length >= 32768 (32KB)
reproduction:
CREATE TABLE NEW_TABLE (
ID INTEGER NOT NULL,
BLOB_FIELD BLOB SUB_TYPE 1 SEGMENT SIZE 80
);
UPDATE NEW_TABLE SET BLOB_FIELD =
'012345678901234567890123456789012345678901234567890123456789012
345678901234567890123456789012345678901234567890123456789012345
--------------------------- skipped, total length >= 32768 bytes ..........................................
345678901234567890123456789012345678901234567890123456789012345
12345678'
Commits: 7802ff6
====== Test Details ======
Confirmed crash on 2.0.6.
No sense to made test for versions < 2.5.
As of 2.5.5, it allows to use single command (e.g., UPDATE TEST SET B='...') with total length up to 65536 characters (from 1st letter `U` in its word "Update" to final single quote). But this limit recently was reduced in 3.0 to 32767 bytes. Thus, test may be done after issuing 3.0 RC.
23.04.2016: 3.0 handles statement with string literal length <= 65535.
The text was updated successfully, but these errors were encountered: