Firebird Documentation IndexFirebird 3.0.2 Release Notes → Bugs Fixed
Firebird Home Firebird Home Prev: Remote Client RecognitionFirebird Documentation IndexUp: Firebird 3.0.2 Release NotesNext: Firebird 3.0.1 Release: Bug Fixes

Bugs Fixed

Table of Contents

Firebird 3.0.2 Release: Bug Fixes
Firebird 3.0.1 Release: Bug Fixes
Firebird 3.0.0 Release: Bug Fixes
Firebird 3.0 Release Candidate 2: Bug Fixes and Minor Improvements
Firebird 3.0 Release Candidate 1: Bug Fixes and Minor Improvements
Firebird 3.0 Second Beta Release: Bug Fixes
Firebird 3.0 Second Beta Release: Improvements
Firebird 3.0 First Beta Release
Firebird 3.0 Second Alpha Release
Firebird 3.0 First Alpha Release

Firebird 3.0.2 Release: Bug Fixes

The following bug fixes were reported prior to the v.3.0.2 official release:

Core Engine

(CORE-5501)     Diagnostics form gstat were unclear when a damaged page in DB file appeared encrypted.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5498)     It was not possible to create a connection for events processing.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5496)     Creating SRP SYSDBA with explicit admin (-admin yes in gsec or grant admin role in create user) was creating two SYSDBA accounts.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5489)     Performance for NULLs filtering inside a navigational index scan was poor.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5474)     The setting 'Restrict UDF' for configuration parameter UdfAccess was ineffective because of fbudf.so being dynamically linked against libc.

fixed by A. Peshkov, A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5472)     Problems with dbcrypt key transfer.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5470)     Trace INCLUDE_FILTER with [[:WHITESPACE:]]+ would not work when a statement was issued that contained a newline character.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5464)     An access violation would occur in fbclient when reading a BLOB stored in incompatible encoding.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5457)     Bugcheck 167 (invalid SEND request).

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5456)     When attempting to migrate a database from Firebird 2.5.2 to 3.0.1, gbak restore would always crash at the end.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5452)     A segmentation fault would occue when the engine's dynamic library was unloaded right after closing worker threads (GC and/or cache writer).

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5448)     Bugcheck oocurred when creating a view on a table that has a column with character set NONE, database default charset is UTF8, and the default collation is UNICODE.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5447)     EXECUTE STATEMENT <e> when <e> starts with '--' (comment) issues “Unexpected end of command” error with a wrong column number.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5432)     Classic Server suffered a performance regression: too much time was being spent during context switches.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5422)     The error “Decompression overran buffer” could occur after rollback. It affected all platforms but would appear particularly on Windows Superserver, when GCPolicy was set to 'Combined' or 'Cooperative' and CpuAffinityMask was configured to more than a single core.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5421)     Performance degradation in FB 3.0.2 compared to FB 2.5.7.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5414)     Error restoring on FB 3.0 from FB 2.5 backup: bugcheck 221 (cannot remap).

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5410)     Dependencies were not stored when certain types of construction were used in subroutines.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5393)     Optimization was poor for some operations with views containing subqueries.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5392)     BUGCHECK 179 (decompression overran buffer) or an unexpected lock conflict could happen during back-out of record versions.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5390)     isql would crash with corrupt memory when statement length exceeded 10 MB.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5384)     Plug-in manager was failing to provide the appropriate config information when the name of the configuration file was set in plugins.conf.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5383)     Dependencies in PSQL packages were not being recognised.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5382)     An SQL statement longer than 10MB could be processed (truncated) incorrectly.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5381)     Regression: A (select from view with nested view) query could not be executed.

fixed by D. Yemanov

    ~ ~ ~     

(CORE-5368)     Regression: a client application could hang or throw an access violation on selecting from multiple threads using one embedded connection.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5367)     Regression: A BOOLEAN state as a parameter for a search condition was incorrectly rejected as invalid.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5366)     Regression: A CASE expression with more than 255 conditions was being rejected.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-5350)     An assertion was exhibited on Windows in CachedMasterInterface::set.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-5314)     UDFs declared with large varchars were taking excessive time to execute.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

(CORE-3530)     BETWEEN operand/clause was not supported for COMPUTED BY columns -- “feature is not supported”. Now it is.

fixed by D. Yemanov

    ~ ~ ~     

Server Crashes/Hang-ups

(CORE-5428)     An old bug could occasionally cause a segmentation fault in Classic when the structure of a table with triggers was modified (DDL) while another attachment was preparing a request to work with that table. In rare cases, pointers to the old triggers were cached by the request compiler and the fault would occur the next time they were used.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5425)     A load test was hanging the server.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5417)     The engine could hang if an automatic sweep was starting during a database shutdown.

fixed by V. Khorsun

    ~ ~ ~     

(CORE-1894)      (Old bug) Circular dependencies between computed fields would crash the engine.

fixed by A. dos Santos Fernandes

    ~ ~ ~     

Builds

(CORE-5120)     Issues with the function snprintf (in autoconfing_msvc.h) and user-defined literals in VS 2015 (MSVC 14).

fixed by V. Khorsun

    ~ ~ ~     

API

(CORE-5359)     New API - MessageMetadata's getScale() was returning INTEGER, while MetadataBuilder's setScale() expected unsigned.

fixed by A. Peshkov

    ~ ~ ~     

POSIX Only

(CORE-5503)     Classic Server was limited to 64 connections when using systemd init scripts

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5484)     A database on an NFS share was unavailable when accessed using the mount point path.

fixed by A. Peshkov

    ~ ~ ~     

(CORE-5458)     Connections were failing due to dead NFS mount points.

fixed by A. Peshkov

    ~ ~ ~     

Windows Only

(CORE-5477)     Trace was duplicating ascii_char(13) in its output on Windows.

fixed by V. Khorsun

    ~ ~ ~     

Prev: Remote Client RecognitionFirebird Documentation IndexUp: Firebird 3.0.2 Release NotesNext: Firebird 3.0.1 Release: Bug Fixes
Firebird Documentation IndexFirebird 3.0.2 Release Notes → Bugs Fixed