Contact Us | Site Map
Firebird is used by approximately 1 million of software developers worldwide. High compatibility with industry standards on many fronts makes Firebird the obvious choice for developing interoperable applications for homogeneous and hybrid environments.
Developer's Report: Firebird Core Development
December 2010 to February 2011

December 2010

TRUNK
  • Frontport fix for bug CORE-3119 : 100% CPU USAGE with Unilimited Loop & Index corrupted
  • Frontport better fix for bug CORE-3266 : Race condition between async service detach request and running user trace service
B2_5_Release
  • Fixed bug CORE-3119 : 100% CPU USAGE with Unilimited Loop & Index corrupted
  • Better fix for bug CORE-3266 : Race condition between async service detach request and running user trace service
  • Fixed bug CORE-3282 : EXECUTE STATEMENT parses the SQL text using wrong charset
B2_1_Release
  • Backport fix for bug CORE-3119 : 100% CPU USAGE with Unilimited Loop & Index corrupted
  • Backport related fixes from v2.5 :
    • Added timeouts to the network event listener code.
    • Fixed wrong usage of SO_REUSEADDR on Windows.
  • Fixed bug CORE-3285 : 100% CPU load
January 2011

TRUNK
  • Front ported fix for bug CORE-3282 : EXECUTE STATEMENT parses the SQL text using wrong charset
  • New build system :
    • Make it compiles on Windows after Alex's changes.
    • Fixed main reason of AV at engine DLL unload time. More fixes will follow soon.
    • Refactor open events cache to avoid atexit handler which could crash process on DLL unload.
  • Fixed bug CORE-3315 : Audit plugin records a sencond *FAILED* EXECUTE_STATEMENT_FINISH after a "normal" one
  • Fixed bug CORE-3095 : Client receive event's with count equal to 1 despite of how many times EVENT was POSTed in same transaction
B2_5_Release
  • More conservative fix for CORE-3282 : EXECUTE STATEMENT parses the SQL text using wrong charset. Convert into attachment charset query text only
  • Fixed bug CORE-3315 : Audit plugin records a sencond *FAILED* EXECUTE_STATEMENT_FINISH after a "normal" one
  • Fixed bug CORE-3095 : Client receive event's with count equal to 1 despite of how many times EVENT was POSTed in same transaction
B2_1_Release
  • Backport fix for bug CORE-3095 : Client receive event's with count equal to 1 despite of how many times EVENT was POSTed in same transaction
February 2011

TRUNK
  • Move VALIDATE_LOCK_TABLE from lock.h into lock.cpp : at allows to rebuild just lock.cpp if some need to disable validation of lock table in DEBUG build or enable validation in RELEASE build.
  • Front ported improvement CORE-3323 : Ability to cancel waiting in lock manager
  • Improvement CORE-3324 : ftracemgr should flush its output from time to time
  • Fixed bug CORE-3325 : At high load it is possible that new process could fail to map shared memory
  • Fixed bug CORE-3326 : Fast mutex could be left in locked state by dead process
  • Fixed bug CORE-3327 : Thread pool in network server could create more threads than necessary
  • Fixed problem with GTT's reported by Adriano in fb-devel
  • Fixed bug CORE-3349 : Constants isc_lock_conflict / isc_eds_statement not recognized in PSQL
  • Fixed bug CORE-3351 : Windows client could put 10054 error messages into firebird.log at connection time
  • Fixed bug CORE-3125 : AV in Worker::shutdown
  • Implement improvement CORE-3362 : Cursors should ignore changes made by the same statement
  • New feature CORE-3364 : Blob filter to translate internal debug info into text representation Additional patch for CORE-3362 : Cursors should ignore changes made by the same statement
  • System requests should run with valid attachment assigned
B2_5_Release
  • Move VALIDATE_LOCK_TABLE from lock.h into lock.cpp : at allows to rebuild just lock.cpp if some need to disable validation of lock table in DEBUG build or enable validation in RELEASE build.
  • Improvement CORE-3323 : Ability to cancel waiting in lock manager
  • Improvement CORE-3324 : ftracemgr should flush its output from time to time
  • Fixed bug CORE-3325 : At high load it is possible that new process could fail to map shared memory
  • Fixed bug CORE-3326 : Fast mutex could be left in locked state by dead process
  • Fixed bug CORE-3327 : Thread pool in network server could create more threads than necessary
  • Fixed bug CORE-3349 : Constants isc_lock_conflict / isc_eds_statement not recognized in PSQL
  • Fixed bug CORE-3351 : Windows client could put 10054 error messages into firebird.log at connection time
  • Fixed bug CORE-3125 : AV in Worker::shutdown
  • System requests should run with valid attachment assigned
B2_1_Release
  • Fixed bug CORE-3351 : Windows client could put 10054 error messages into firebird.log at connection time
B2_0_Release
  • Fixed bug CORE-3351 : Windows client could put 10054 error messages into firebird.log at connection time
Vladyslav Khorsun
Dnetpropetrovsk, Ukraine
Join Firebird!
RSS Newsletter
Home About Firebird Documentation Downloads Community Support Development Case Studies Back to Top
This site and the pages contained within are Copyright © 2000-2017, Firebird Project. Firebird® is a registered trademark of Firebird Foundation Incorporated. Developed by DQ Team.