Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
19.2.0
-
EPAM-Veg Sprint 100, EPAM-Veg Sprint 101
-
Vega
-
Q3 2020 Bug Fix
Description
Overview:
mod-circulation v19.2.0 seems to have an easily reproducible memory leaks issue. When starting up the module without sending any requests to it, mod-circulation gobbles up memory, from 60% to 100%. When put it under a 8-users check-in-check-out test, mod-circulation continually taking memory without putting it back, resulting in the Docker containers crashing after 30 minutes of running the test. Longevity test of v19.1.0-SNAPSHOT also showed leaks, but slower than 19.2.0. Heap dump of memory leaks showing HTTPClientImpl objects being the main culprit.
Steps to Reproduce:
- Run any repetitive workflow tests, get RTAC or check in/out with 1-8 users for half an hour and mod-circulation's memory utilization will increase easily.
Expected Results:
No memory leaks observed
Actual Results:
Memory leaks observed, docker containers crashed in a 30 minutes test.
Additional Information:
URL: Please see the last comment by Roman Fedynyshyn on PERF-123 detailing the findings of mod-circulation v19.2.0 memory leaks.
Interested parties: marcjohnson cboerema
TestRail: Results
Attachments
Issue Links
- duplicates
-
CIRC-969 Event publishing causes memory leak
-
- Closed
-
- is blocked by
-
MODPUBSUB-127 HttpClientImpl instances created by PubSubClient are not closed explicitly
-
- Closed
-
-
MODPUBSUB-128 Release v1.3.1
-
- Closed
-
- relates to
-
CIRC-1121 Investigate Memory Leaks, HttpClients
-
- Closed
-
-
PERF-123 Investigate pre-honeysuckle mod-circulation memory leaks
-
- Closed
-
-
CIRC-863 SPIKE: Investigate mod-circulation memory leaks (Goldenrod)
-
- Closed
-
-
CIRC-969 Event publishing causes memory leak
-
- Closed
-
-
EDGRTAC-33 Memory leak of ~200mb for /rtac?instanceIds=id1,id2,idn API
-
- Closed
-