Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Trace Compass/News/NewIn42"

(Created page with "= Bugs fixed in the 4.2.0 release =")
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
= Trace Compass tutorials =
 +
Tutorials on how to use Trace Compass for trouble-shooting various reliability problems are now available and a link can be found on the [https://www.eclipse.org/tracecompass/#docs Trace Compass website].
 +
 +
=Improved support for dark theme=
 +
In this version of Trace Compass, initial support of the Eclipse dark theme has been added. This improves the user experience when using the dark theme. Colors of lines in XY chart views, state colors in Time Graph views or cursors colors are not updated for that. More updates are needed to fully be able to style Trace Compass for the dark theme.
 +
 +
[[File:TC-DarkTheme.png]]
 +
 +
=Detection of potential memory leaks=
 +
 +
This "Potential Memory Leak" view shows where in the trace was allocated memory that was not deallocated during the trace time. These are not necessary leaks, for real leaks, tools like Valgrind are preferable, but used in conjonctions with other views like the "Flame Chart", it can help find where in the code this memory was allocated.
 +
[[file:memoryleak.png]]
 +
 +
[[file:memoryleak2.png]]
 +
 +
=Change default zoom per trace type=
 +
 +
Allow the user to change the default zoom level of a given trace type, this can be accessed via the Tracing->Trace Types menu in Preferences.
 +
 +
[[File:change-default-zoom.gif]]
 +
 +
=Provisional APIs to support traces in JSON format=
 +
Provisional APIs have been added for Trace Compass adopters to parse traces written in JSON format. With this it will be possible to implement JSON trace types. The source code provides a way to sort a JSON trace per timestamp if the trace events are not in chronological order. For example, the support for Jaeger traces in the Trace Compass incubator project already uses these APIs. The APIs are currently provisional, to allow further refinement of the API later on and allow for early adopters to give feedback.
 +
 +
=Data-driven analysis (XML) improvements=
 +
* Improved documentation
 +
 +
* Add support for "duration"s allowing developers to make a segment/state from a single input.
 +
 +
=Critical Path improvements=
 +
 
= Bugs fixed in the 4.2.0 release =
 
= Bugs fixed in the 4.2.0 release =
 +
See Bugzilla report [https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&classification=Tools&product=Tracecompass&query_format=advanced&resolution=FIXED&target_milestone=4.2.0 Bugs Fixed in Trace Compass 4.2.0]

Revision as of 11:24, 20 December 2018

Trace Compass tutorials

Tutorials on how to use Trace Compass for trouble-shooting various reliability problems are now available and a link can be found on the Trace Compass website.

Improved support for dark theme

In this version of Trace Compass, initial support of the Eclipse dark theme has been added. This improves the user experience when using the dark theme. Colors of lines in XY chart views, state colors in Time Graph views or cursors colors are not updated for that. More updates are needed to fully be able to style Trace Compass for the dark theme.

TC-DarkTheme.png

Detection of potential memory leaks

This "Potential Memory Leak" view shows where in the trace was allocated memory that was not deallocated during the trace time. These are not necessary leaks, for real leaks, tools like Valgrind are preferable, but used in conjonctions with other views like the "Flame Chart", it can help find where in the code this memory was allocated. Memoryleak.png

Memoryleak2.png

Change default zoom per trace type

Allow the user to change the default zoom level of a given trace type, this can be accessed via the Tracing->Trace Types menu in Preferences.

Change-default-zoom.gif

Provisional APIs to support traces in JSON format

Provisional APIs have been added for Trace Compass adopters to parse traces written in JSON format. With this it will be possible to implement JSON trace types. The source code provides a way to sort a JSON trace per timestamp if the trace events are not in chronological order. For example, the support for Jaeger traces in the Trace Compass incubator project already uses these APIs. The APIs are currently provisional, to allow further refinement of the API later on and allow for early adopters to give feedback.

Data-driven analysis (XML) improvements

  • Improved documentation
  • Add support for "duration"s allowing developers to make a segment/state from a single input.

Critical Path improvements

Bugs fixed in the 4.2.0 release

See Bugzilla report Bugs Fixed in Trace Compass 4.2.0

Back to the top