Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Futex Contention Latency Analysis
The Futex Contention Latency Analysis measures the futexes contention latency between futex entry and exit event for a thread. The durations are visualized using the Latency views. For more information about the Latency views see chapter Latency Analyses in the user guide.
The following views are also available for the Futex Contention Latency Analysis:
Uaddr vs Waiter
A timegraph view of the waiters by futex uaddr. This view is useful to see which threads are waiting on a specific futex and understand blocked threads.
A timegraph view of the futex wait/lock and wake/unlock scenarios (from futex entry to futex exit). This view is useful to suss up the general level of contention in a given trace. It highlights futex lifespans.
For more information about the Futex Contention Latency Analysis see the chapter Futex Contention Latency Analysis or the Trace Compass user guide.
It is now possible to define a default perspective in the extension of the trace type UI extension point. When a default perspective is define for a given trace type and the perspective is not currently open, then a dialog window opens to confirm switching the perspective during opening of a trace.
The user's choice is persisted as part of the tracing preferences and can be changed using Window -> Preferences... -> Tracing -> Perspectives preference page.
This has been implemented for the trace types LTTng Kernel, Network pcap and GDB Trace trace types that are delivered by this release.
Support of trace aspects in XML analysis
Trace aspects are used to populate the columns of the events table. Some traces have aspects to show special data in a column that cannot be directly retrieved from the event content. Now it's possible to use the aspect name (column name) to retrieve the aspect value through the event field keyword.
Preparation for removal of deprecated APIs in Oxygen release
After Trace Compass 2.3 release all APIs that have been deprecated by the 2.3 release will be removed. Please make sure that plug-in extensions to Trace Compass are updated before upgrading to 3.0 (Oxygen release).
Bugs fixed in the 2.3.0 release
See Bugzilla report Bugs Fixed in Trace Compass 2.3.0