This roadmap shows the work that we have planned for the next few quarters. Only the major features are displayed on this roadmap. Maintenance, support issues and crash fixes are part of our daily routine. Of course, nothing is set in stone — we continuously evaluate the priorities of our work based on customer feedback and internal planning.
If there is anything that is missing or you want to give input on any of these features, don’t hesitate and let us know!
Management of captured profiles
People reported that they would like to manage their profiles better: rename/delete and get extended information about them. In some situations, when the recent files/recent runs become very long, problems with the UI occur. We are planning a redesign of the start pages to accommodate these issues.
‘All threads’ option in the callgraph
One of the most requested features is to be able to view callgraph information from multiple threads at the same time. This is very useful when job systems schedule work over many threads at the same time.
.NET (C#) support
We are planning to support C# and the .NET framework in Q4 of 2020.
Thread management in timeline view
Users reported that they would like to have more control over the threads in the timeline view: hiding them, sorting them manually. Also, the default sorting (which we try to do as well as we can, based on activity) does not always work as well as we’d like to.
Child process support
Currently, only a single process can be captured. Often, processes spawn child processes to offload work. We are planning a feature to see a process along with all its child processes and how they communicate with each other.
Improvements to the licensing system
Many of our users add more licenses over time, but for each newly purchased license, they receive a new key. After a while, the management of all those separate keys becomes tedious. We plan to make it easier for customers to manage their licenses. We will also be looking at an interface where activations for licenses can be managed.
Symbol resolving view
The number one support request we receive is about symbol resolving: if symbols aren’t properly resolved, what symbol files are being tested, and why aren’t they matching? To make this more transparent to users, we plan to add a view where this becomes visible. Also, we want users to be able to add a symbol path and re-process a session with modified symbol paths.
Improvement to the Find Results Window
Currently, users report that they would like a better way to navigate the find results. Although the design is pending, we plan to be able to have an extended find window where it is easier to browse the find results, see timings and select them.
Recursion folding in CallGraph
CallGraphs are hard to navigate when code recurses. We plan to offer an option to ‘fold’ recursion per node in the CallGraph so that the collapsed costs can be viewed instead.