getappmap / getappmap/appmap-java
Out of heap space on a Java project with a Maven build
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 88
- Forks
- 17
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 1
Description
Please see the build results from a SchemaCrawler build with AppMap recording. The Maven build on a Java project consistently runs out of heap space. This has never happened without AppMap recording turned on.
https://github.com/schemacrawler/SchemaCrawler/runs/6084237189?check_suite_focus=true
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked SchemaCrawler build results and compare the Maven build behavior with AppMap recording enabled and disabled. Determine what causes the Java project to exhaust heap space during recording; done means the build no longer runs out of heap with AppMap enabled and the relevant behavior is covered by evidence or a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100