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

Bugcheck 179 (decompression overran buffer) when attempting to update the same record multiple times [CORE1958] #2396

Closed
firebird-automations opened this issue Jun 24, 2008 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

Is duplicated by CORE1968

Let's have some record stored in a longer format while the current format is shorter. If this record is updated multiple times within a single transaction and then a savepoint cleanup happens (e.g. due to some runtime error related to another data), then a bugcheck can happen. This seems to be caused by the lack of sync between actual record length on disk (new version will have a short format) and rec_length field of new_rpb->rpb_record which may keep the longer value (from some prior operations with another format).

Commits: 068b83e 3f367c6 fe2e2ed

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Open [ 1 ]

Fix Version: 2.5 Beta 1 [ 10251 ]

Fix Version: 2.1.2 [ 10270 ]

Fix Version: 2.0.5 [ 10222 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is duplicated by CORE1968 [ CORE1968 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

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