A memory leak analysis
Github repository with getting-started
Tag 1.12.1 contains the memory leak under investigation
Tag 1.12.2 has the issue fixed!
-
Remove files to the minimum
-
Log something to expose the issue
- For this example we use the default logger
org.jboss.logging.Logger
- Quarkus uses JBoss Log Manager and the JBoss Logging facade.
- For this example we use the default logger
-
Create a load test
- For this example we used jmeter-java-dsl
- check BasicLoadTest.java
cd code
mvn clean install
mvn clean install -P withoutIssue
java -jar target/quarkus-app/quarkus-run.jar
Open your browser and validate
java -Xms100m -Xmx100m -jar target/quarkus-app/quarkus-run.jar
The test written using jmeter-java-dsl
cd load-test
mvn test
google-chrome html-report/index.html