FB TraceManager Changelog

What's new in FB TraceManager 3.5.3.7

Oct 10, 2014
  • Enhancements:
  • Add support for additional Firebird 3 Beta 1 ODS 12.0 monitoring tables additions.
  • Make provided monitoring tables and grid columns aware of the connected database ODS.
  • Restore "Font size" setting for Raw trace data area upon trace session startup.
  • Bug fixes:
  • Bug fixed: First program startup for new installations may fail with an database error while upgrading metadata.
  • Bug fixed: Column header text may overwrite previous column text.
  • Bug fixed: Open Analysis cube may fail when executing for analysis entries with different SQL statements.

New in FB TraceManager 3.5.2.10 (Sep 30, 2014)

  • Enhancements:
  • Enhance UI docking capabilities across the entire product.
  • Update deployed Firebird embedded to V2.5.3.
  • Support for Firebird 3 "explain_plan" trace configuration option.
  • Allow per server Trace UI layout restoring regarding splitter positions.
  • Bug fixes:
  • Bug fixed: Form layout in Trace UI is sometimes screwed up upon connecting to the server.

New in FB TraceManager 3.5.1.8 (Apr 28, 2014)

  • Enhancements:
  • Purging of trace data: Support for purging of stored data in "Browse" module.
  • "About" menu item on the left in the main form to show the splash screen.
  • Bug fixes:
  • Bug fixed: Random AV when double-clicking in parsed trace data grid.
  • Bug fixed: "Go To Raw Line" navigation in parsed trace data grid jumps to wrong raw line.
  • Bug fixed: Random AV when deleting a project.

New in FB TraceManager 3.5.0.18 (Feb 26, 2014)

  • Firebird 3 Support
  • Performance Improvements
  • Increased RAM usage limit to 3GB/4GB
  • Usability Improvements
  • Bugfixes, improved stability

New in FB TraceManager 3.0.2.11 (Oct 29, 2013)

  • Enhancements:
  • Expose and persist a "Has Garbage Collection" flag in parsed trace data based on the values in Detailed Statistics. (#0000740)
  • Expose and persist Garbage Collection total counters for Backout, Purge, Expunge in parsed trace data. (#0000741)
  • Expose and persist a "Has Garbage Collection" flag in Record Statistics tab in Monitoring Tables integration. (#0000742)

New in FB TraceManager 3.0.1.61 (Oct 29, 2013)

  • Expose and persist a "Has Garbage Collection" flag based on the values in Detailed Statistics. (#0000740)
  • Bug fixes:
  • Noticeable performance degradation in raw output after a first purge cycle. #0000588
  • Code Folding in raw output doesn't work. #0000589

New in FB TraceManager 3.0.0.58 (Oct 29, 2013)

  • Enhancements:
  • Upgrade included Firebird Embedded Engine to V2.5.2. #0000489
  • Support for parsed Detailed Statistics in trace data. #0000514
  • Support for parsed sweep transaction counters in trace data. #0000516
  • Visualize percentage columns in various data grids with an additional progress/percentage bar. #0000517
  • Database Statistics: Add percentage of table and index size related to database size. #0000524:
  • Percentage of table size related to the database size
  • Percentage of index size related to total index size of database
  • Percentage of index size related to total index size per table
  • Add ability to view parsed trace column data in a separate modal dialog. Available in the parsed trace data grid context menu. #0000525
  • Support for parsed Bind Variables in trace data. #0000527
  • On-The-Fly "Statement Hotspot" view per active trace session added. The "Statement Hotspot" is an aggregated view on executed SQLs with various useful measures/counters (e.g. Execution Count vs. Prepare Count, number of distinct transactions per SQL, number of distinct execution plans per SQL and a lot more). Data is aggregated on-the-fly (incrementally) while the EXECUTE_STATEMENT_FINISH event is captured. Make sure to include the following trace configuration options, to fully take advantage of this new feature: log_statement_prepare, log_statement_free, log_statement_start, log_statement_finish. #0000540
  • Re-arrange Registered Projects and Trace Session List areas to the upper client area. #0000541
  • Database Statistics: Make index statistics detection dependent on a configurable number of nodes. Default value: 10000. #0000542
  • Add SEVERITY information/column in Header Page and Database Statistics Monitoring. This will help to spot potential problems in header page and table/index statistics more quickly. #0000543
  • Database Statistics: Make table statistics detection dependent on a configurable number of records. Default value: 10000. #0000544
  • Parser throughput has been improved considerably. #0000563
  • Visualization throughput has been improved considerably. #0000567
  • "Paused" / "Dismissed when paused" option per visualization is now a global setting per trace tab. #0000568
  • Add "Skipped Events" in Statistics tab of a trace session tab. This counts the number of skipped events in case of the Dismiss when paused option. #0000569
  • Custom Trace Configuration Template storage. This allows to define templates/presets of trace configurations for later re-use in the Project Wizard. #0000571
  • Disabled Trace Vizualisation mode, which results in a very light-weight trace processing with Hotspots data only. #0000572
  • Removed Chart Trace Visualization as it doesn't provide any additional value. More useful charting to be expected in forthcoming releases. #0000573
  • Support for Firebird Embedded as Traceable Server. #0000585:
  • Bug fixes:
  • Charting in active trace session isn't purged like parsed trace data, thus prevents FBTM from running 24x7. #0000491
  • Random AV when closing an established database connection tab. #0000495
  • Random AV when closing an established server attachment tab. #0000496
  • Minor memory leak in internal structures in the per-database monitoring area. #0000515
  • Apply index statistics problem detection on live index metadata columns doesn't make sense when loading from file. #0000545
  • AV when loading header page gstat output only from file in Database Statistics. #0000547
  • Database Statistics: Minor glitch that Index Management is enabled where it shouldn't. #0000548
  • Random AV and/or lockups when closing a trace session tab while it's in the middle of processing trace data. #0000566
  • AV when Firebird server can't start a trace session due to missing trace plugins. #0000586
  • Random AV when duplicating a project with a server as target with no registered databases. #0000587

New in FB TraceManager 2.5.4.9 (Jul 31, 2012)

  • Enhancements:
  • Support for new Firebird 2.5.2 "log_sweep" trace configuration parameter
  • Support for new Firebird 2.5.2 SWEEP_* trace events
  • Bug fixes:
  • Bug fixed: -1 is stored for RemoteProcessId, if remote process information is not available.

New in FB TraceManager 2.5.3.8 (Jul 31, 2012)

  • Enhancements:
  • Support for new Firebird 2.5.2 "log_errors" trace configuration parameter
  • Support for new Firebird 2.5.2 ERROR AT, WARNING AT trace events
  • Bug fixes:
  • Bug fixed: Trace data parser issue when the term "Statement" is part of the remote process name.
  • Bug fixed: AV when Firebird server returns "Error creating trace session" in case of not being able to start a trace session.

New in FB TraceManager 2.5.2.11 (Jul 31, 2012)

  • Enhancements:
  • Support for Firebird 3 trace configuration format.
  • Support for specifying the Firebird client library at different levels, e.g. in the program configuration for the FBTM2.fdb attachment, server and database registration to be used when attaching to the trace service, for per-database monitoring etc.
  • Docking capabilities ala Visual Studio across the product.
  • Bug fixes:
  • Bug fixed: Double-quotes in exported CSV isn't escaped properly.
  • Bug fixed: Random AVs, freezes.
  • Bug fixed: Regression causing the trace raw memo output flickering / repainting a lot

New in FB TraceManager 2.5.1.35 (Jul 31, 2012)

  • Enhancements:
  • Additional per-database monitoring facility called "Database Statistics". This integrates more gstat like output, e.g. data pages, index pages, record versions etc.
  • Support for ODS 11.1 (Firebird 2.1) monitoring tables. Monitoring tables integration failed with an ODS 11.1 database, because FBTM expected a Firebird 2.5 database with ODS 11.2.
  • When registering a new server database, pre-set username/password from the server entry.
  • Support for database size (KB, MB, GB) in "Database" monitoring tables tab.
  • Ability to fetch the database default character set when registering a database.
  • Improved performance when closing areas where data grid states are persisted.
  • Export To CSV: Support in trace data grid and all data grids in per-database monitoring.
  • Load database header page from file including processing.
  • Improved performance when filling monitoring table grids.
  • Pre-select useful trace configuration when creating a new trace project.
  • Reworked/added context-menus in Database Monitoring area.
  • One-Click functionality to locate OAT from the header page output in the transaction monitoring table.
  • Allow re-arranging grid column positions in the grid configuration dialog.
  • Bug fixes:
  • Bug fixed: Minor problem in context-sensitive filtering in monitoring table grids.
  • Bug fixed: Duplicating a server/database entry while it's in connected state, results in unusable new server/database nodes.
  • Bug fixed: Appending "- Copy" for server host and database name when duplicating doesn't make sense.
  • Bug fixed: In Monitoring Statements: TransactionID = 0 and Timestamp = 30.12.1899 for empty entries.

New in FB TraceManager 2.5.0.35 (Feb 16, 2012)

  • Enhancements:
  • Per-database monitoring capabilities including header page monitoring and Firebird MON$ tables integration.
  • Database views for easier access to query logon/logoff trace data information.
  • Allow to specify a trace column definition file in the trace project.
  • More appealing way to manage trace session options for an active trace session by using flyout tool panels.
  • Flyout toolbar panel states are now persisted.
  • Attempt to make FB TraceManager more Firebird 2.5.1 friendly. Not entirely sure if this works reliably.
  • Increase page buffers value of the FBTM database to 1024. Applies only to new installations. Feel free to adjust the page buffers value for your installation as needed.
  • Bug fixes:
  • Bug fixed: Refreshing the registered server area (e.g. when editing a server entry) will lose the connected state of servers.
  • Bug fixed: FBTM database metadata update might fail, when there are others connections active. Now there is a check in-place, that a metadata update is only executed, if there are no other active connections on the database.
  • Bug fixed: Exception "A component named tsStartedProject ..." when starting a trace session

New in FB TraceManager 2.0.8.5 (Feb 16, 2012)

  • Enhancements:
  • Purge strategy for raw and parsed trace data implemented to allow FB TraceManager running in 24x7 scenarios. More information on the new project-based options Raw Max Lines, Parsed Max Rows and Parsed Purge Rows is available in the Trace Data Visualization section.
  • Bug fixes:
  • Bug fixed: "Access violation at address 00000000. Write of address 00000000." in random situations.
  • Bug fixed: FBTMLoggerSvc: Parsed trace event is always one event behind.

New in FB TraceManager 2.0.7.1 (Dec 2, 2011)

  • Enhancements:
  • Support for EXECUTE_BLR trace event. (#0000195)
  • Bug fixes:
  • Bug fixed: Main window state is always maximized, thus ignores the previously used position and size. (#0000194)

New in FB TraceManager 2.0.6.1 (Dec 2, 2011)

  • Bug fixes:
  • Bug fixed: Parser: Execution time in EXECUTE_PROCEDURE_FINISHED processed wrongly. (#0000185)
  • Bug fixed: Parser: Number of reads/writes etc ... in COMMIT_RETAINING not processed. (#0000186)
  • Bug fixed: Parser: Number of reads/writes etc ... in ROLLBACK_RETAINING not processed. (#0000187)
  • Bug fixed: "Number of records fetched" is stored as -1 when it should be 0. (#0000188)
  • Bug fixed: Another potential AV upon stopping a busy trace session. (#0000189)
  • Bug fixed: Trace data storage transacion isn't committed when stopping a trace session via the trace session list. (#0000190)

New in FB TraceManager 2.0.5.0 (Dec 2, 2011)

  • Bug fixes:
  • Bug fixed: Problem in parser handling parameters and detailed statistics for EXECUTE_PROCEDURE_FINISH. (#0000182)
  • Bug fixed: Problem in parser handling parameters and detailed statistics for EXECUTE_STATEMENT_FINISH. (#0000183)
  • Bug fixed: Problem in parser handling number of reads/writes etc. for EXECUTE_PROCEDURE_FINISH. (#0000184)

New in FB TraceManager 2.0.4.0 (Dec 2, 2011)

  • Bug fixed: Memory usage steadily increases even without visualization enabled. E.g. in the logger Windows service or in the application if "Paused" and "Dismiss when Paused" = ON in the visualization, thus memory usage shouldn't increase in this case. This makes the Windows logger service FBTMLoggerSvc capable to run 24x7 without significant memory usage. The fix also affects FB TraceManager, because less memory is used when adding a lot of trace events to the raw and parsed output. (#0000181)

New in FB TraceManager 2.0.3.5 (Dec 2, 2011)

  • Enhancements:
  • New event rule type "OnExecuteApplication" for executing an application has been added in the Event Processing module. (#0000175)
  • New event rule type "OnPlaySound" for playing a (system) sound has been added in the Event Processing module. (#0000176)
  • Bug fixes:
  • Bug fixed: Possible crash in the Trial Edition after exceeding the max. number of allowed parsed trace events. (#0000177)

New in FB TraceManager 2.0.2.8 (Dec 2, 2011)

  • Project-based "re-sort" option for re-sorting newly added parsed rows automatically. (#0000155)
  • Allow to set footer band column value as column regex filter. (#0000156)
  • In query result set (used in Browse, Reporting, Analysis): Show real CLOB/Memo field content instead of WIDEMEMO. (#0000167)
  • Improved application responsitivity with busy trace sessions. (#0000169)
  • Replaced memory manager which results in overall slightly improved performance. (#0000170)
  • Project-based "Dismiss when paused" option to remove received trace events from the queue when visualization is paused. (#0000173)
  • Bug fixes:
  • Bug fixed: Regex filter in parsed grid fails for input values containing regex filter escape characters. (#0000157)
  • Bug fixed: Another race condition when post-processing certain event types leads to trace session abort. (#0000158)
  • Bug fixed: In Project Wizard: Trace configuration isn't stored when clicking on Finish without visiting the last wizard page. (#0000159)
  • Bug fixed: In Analysis Wizard: "Finish" button isn't enabled after entering a SQL statement. (#0000161)
  • Bug fixed: Crash when closing the application while running trace sessions are busy. (#0000162)
  • Bug fixed: Occasional "List index out of bounds (-1)" error message with busy trace sessions. (#0000163)
  • Bug fixed: Post-processing trace events produces garbage while receiving trace data which leads to exception when log to database is enabled and more. (#0000164)
  • Bug fixed: "List index out of bounds (-1)" error message when working with a selected project, trace session after refreshing the list. (#0000165)
  • Bug fixed: Double-clicking the module (Browse, Reports, ...) menu items instead of a single-click leads to an exception. (#0000166)
  • Bug fixed: FBTMLoggerSvc2: Stored session name is not the logger service session name. (#0000168)

New in FB TraceManager 2.0.1.1 (Dec 2, 2011)

  • Bug fixes:
  • Bug fixed: In case of an application error, the application crashes instead of showing a detailed exception dialog (stack trace). (#0000147)
  • Bug fixed: The exception stack trace file (.elf) isn't placed in the user's application data directory. It now goes into "C:\Users\\AppData\Roaming\FB TraceManager 2" or "C:\Users\\AppData\Roaming\FB TraceManager 2 Lite". (#0000148)
  • Bug fixed: Memory leak per received trace event. (#0000149)
  • Bug fixed: Rare access violations with certain processed trace event types. (#0000150)
  • Bug fixed: Minor memory leaks caused by the Reporting, Analysis and Event Processing module. (#0000151)
  • Bug fixed: Number of allocated threads doesn't decrease when stopping a trace session. (#0000152)
  • Bug fixed: Crash when stopping a busy trace session. (#0000153)

New in FB TraceManager 2.0.0.9 (Dec 2, 2011)

  • Improved multi-threading capabilities. Especially in the area of synchronizing the GUI with received trace data from background worker threads has been re-written. This should consume less CPU and should not starve the main GUI thread. In general, the application should be more responsive when running several trace sessions at the same time now. (#0000105)
  • Minimize to tray option to be found in the Settings. (#0000107)
  • Ability to duplicate a server entry. (#0000108)
  • Support for regular expression filters in trace session and project list. (#0000109, #0000110)
  • Per project option to define the GUI refresh interval (milliseconds) in the newly implemented multi-threading model. (#0000112)
  • The raw output visualization has been improved a lot. (#0000111)
  • Line number
  • New trace event line can be highlighted with a custom background color
  • SQL Syntax-Highlighting
  • Trace event type (PREPARE_STATEMENT, CLOSE_CURSOR ...) keyword highlighting
  • Trace event raw data folding to collapse/expand trace event data
  • Support for bookmarks to navigate to user-definable locations easily
  • Option in Register Server wizard to auto-connect upon program start. (#0000114)
  • Support for all parsed grid columns when copying content to clipboard (context-menu) and not only SQL and execution plan. (#0000116)
  • Append "- Copy" text in certain fields in various wizards when duplicating an entity (project, report, analysis ...). (#0000118)
  • Context menus in report and analysis manager tree view added. (#0000119, #0000120)
  • Footer band in parsed data grid with column-based aggregate functions on numeric columns. (#0000123)
  • Locate line in raw data output for a given parsed trace event by double-clicking (or context-menu) a row in the parsed trace data grid. (#0000125)
  • Temporary queue received trace data/events in case of paused visualization and process upon resume. This makes the "Add invisible row when paused" option obsolete, thus it has been removed. (#0000126)
  • "Cancel" button in transaction active confirmation dialog when closing a trace session tab to cancel closing the tab. (#0000127)
  • GUI improvement: Replace splitter with flyout tool panels were applicable. (#0000132)
  • Added units ([ms], [pages]) in parsed grid column header caption for certain columns (e.g. Execution time ...). (#0000135)
  • Setting a filter in parsed trace data grid from column values in the selected row. (#0000139)
  • Show image/icon in header of parsed trace data grid in case of a filtered column. (#0000140)
  • Bug fixes:
  • Bug fixed: Fixed a bug where the parsed grid output and persisted trace events are always one event behind the raw output. (#0000106)
  • Bug fixed: Fixed a rare race condition when running multiple trace sessions simultaneously. (#0000113)
  • Bug fixed: Rare occasion where a newly added parsed grid row got a white text color. (#0000117)
  • Bug fixed: Potential problem when detecting the Firebird version upon server connect. (#0000121)
  • Bug fixed: Problem with parser for an unauthorized attach database event, as there is no ROLE information in the trace data included. (#0000122)
  • Bug fixed: Rare race condition when pausing visualization while trace data is received/processed. (#0000128)
  • Bug fixed: AV when deleting an event rule which is currently in edit mode. (#0000131)
  • Bug fixed: Parser has problems when post-processing certain event types (e.g. COMPILE_BLR). (#0000134)
  • Bug fixed: In case of an application error, the application crashes instead of showing a detailed exception dialog (stack trace)

New in FB TraceManager 1.6.0.10 (Dec 2, 2011)

  • Windows service based logger application (FBTMLoggerSvc2) has been implemented. It's included in the download package for registerd customers only. Initially it is a trial version and needs to be licensed separately. Check out the FBTMLoggerSvc - Windows Service section. (#0000035)
  • Administration of Windows service based logger has been added to the project wizard. Check out the FBTMLoggerSvc - Getting Started section. (#0000036)
  • Make trace-session based options (log to database, commit interval ...) available per project. (#0000029)
  • Project-based default regex filter values. (#0000032)
  • In the server-based project list: Button Browse Trace Data to jump/navigate to the Browse module for the selected project. (#0000034)
  • Optimize memory usage in trace data parser. Allocates and frees memory more efficiently now. (#0000040)
  • Bug fixes:
  • Bug fixed: FBTM database metadata update sometimes fails. Querying the database version is now properly closed before executing scripts. (#0000033)
  • Bug fixed: Memory leak in trace data parser, which results in out of memory exceptions when running FB TraceManager 2 for a while with active trace sessions. As each trace session holds it's own trace data parser instance, things are getting even worse with an increasing number of active trace sessions. (#0000039)
  • Bug fixed: Minor memory leaks. (#0000050)

New in FB TraceManager 1.5.2.2 (Dec 2, 2011)

  • Option to automatically start trace sessions upon server connect. (#0000015)
  • Multi-select in project grid to enable start/delete of multiple projects. (#0000016)
  • Multi-select in trace session list to resume/suspend/stop multiple trace sessions. (#0000017)
  • Clear regex filter functionality implemented. A button / context-menu item in the parsed trace data grid area allows to clear a defined regex filter. (#0000018)
  • Confirmation dialog to commit active log database transaction in case of closing the trace session tab sheet. (#0000019)
  • Allow regex filter on # column in parsed trace data grid. (#0000020)
  • Show "Finish" button in project wizard in all wizard pages. (#0000026)
  • Bug fixes:
  • Bug fixed: Rare AV when closing FB TraceManager 2 with active trace sessions. (#0000014)