> 7. How well do the ‘Leak Suspects’ and ‘Top Components’ reports work for users? Do they actually show the problems?
I was recently thinking that it would be useful to make the Leak Suspects report extensible. For many users of MAT, the main workflow is: 1) open heapdump, 2) run leak suspects, 3) send the report to the team that owns the main leak suspect.
The current leak suspects report is very good but it sometimes lacks very useful product-level details that MAT cannot be expected to know. Some sort of extension points would be helpful to allow adding new leak suspects, augmenting MAT-generated
leak suspects, and removing leak suspects.
Kevin Grigorenko
IBM Application Runtimes SWAT, Software Engineer
From:
mat-dev <mat-dev-bounces@xxxxxxxxxxx> on behalf of Andrew Johnson via mat-dev <mat-dev@xxxxxxxxxxx>
Date: Wednesday, September 20, 2023 at 7:11 AM
To: mat-dev@xxxxxxxxxxx <mat-dev@xxxxxxxxxxx>
Cc: Andrew Johnson <andrew_johnson@xxxxxxxxxx>
Subject: [EXTERNAL] [mat-dev] Memory Analyzer 1.15.0
I think we should plan for a new release of Memory Analyzer. There is a placeholder target field 1. 15. 0 for Git which I have used for some of the current defect
/ features. https: //bugs. eclipse. org/bugs/buglist. cgi?classification=Tools&list_id=21370820&product=MAT&query_format=advanced&target_milestone=1. 15. 0
I think we should plan for a new release of Memory Analyzer.
There is a placeholder target field 1.15.0 for Git which I have used for some of the current defect / features.
https://bugs.eclipse.org/bugs/buglist.cgi?classification=Tools&list_id=21370820&product=MAT&query_format=advanced&target_milestone=1.15.0
The full unresolved bug and enhancement list is:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;order=Importance;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=MAT
I was thinking of December 2023, to coincide with SimRel 2023-12. Does that give enough time for us, and is that soon enough for users?
Other things to do might be:
- Check how MAT works with Java 21 (LTS), from OpenJDK, Temurin and Semeru (when available), for running with, and analysing dumps from.
- Check we are up to date on dependencies, to avoid security warnings.
- Write a release record at the project page.
https://projects.eclipse.org/projects/tools.mat
- Follow
https://wiki.eclipse.org/MemoryAnalyzer/Contributor_Reference#New_version_development_process
- Follow
https://wiki.eclipse.org/MemoryAnalyzer/Contributor_Reference#Simultaneous_release_policies
I know that no one is working full time on the project – but how and for what can we encourage help from others?
- Documentation – it’s in DITA which might be a bit unclear but is sort of like HTML.
- Do we need an explanation and images of all the views?
- The acquiring a heap dump section needs updates for more recent version of Java.
- Build – is there a Tycho / Maven person who could review our build process? Can we get a dependency check for vulnerabilities, or a software bill of materials?
- Translations – does anyone want MAT translated to another language. MAT is enabled, and translations updates can be made via
https://babel.eclipse.org/ and the results can be installed into MAT. However, all the translations are incomplete, and the best, Japanese, is only 33% translated. We would need people fluent in the target language who
also understand English and MAT well.
- Do we need an automated regression test build?
- Do we need an automated performance test build?
- Should we tag some bugs with keyword=’helpwanted’ ?
- How well do the ‘Leak Suspects’ and ‘Top Components’ reports work for users? Do they actually show the problems?
- Do we need a section on the website explaining how to help the project?
Thoughts, anyone,
Andrew Johnson
Unless otherwise stated above:
IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
