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.
Difference between revisions of "Trace Compass/News/NewIn42"
(→XML improvements) |
(→JSON trace support) |
||
| Line 17: | Line 17: | ||
[[File:change-default-zoom.gif]] | [[File:change-default-zoom.gif]] | ||
| − | =JSON trace support | + | =APIs to support traces in JSON format= |
| − | + | APIs have been add for Trace Compass adopters to parse traces written in JSON format. With this it will be possible to have 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. | |
| + | |||
=Data-driven analysis (XML) improvements= | =Data-driven analysis (XML) improvements= | ||
* Improved documentation | * Improved documentation | ||
Revision as of 16:28, 20 November 2018
Contents
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.
Potential Memory Leak Detector
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.
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.
APIs to support traces in JSON format
APIs have been add for Trace Compass adopters to parse traces written in JSON format. With this it will be possible to have 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.
Data-driven analysis (XML) improvements
- Improved documentation
- Add support for "duration"s allowing developers to make a segment/state from a single input.