bug #7900
closedExcessive heap consuption in RegistrationWorkingsetEditor with big workingsets
100%
Description
Adding a new name to the registration workingset Kulikovskiy, M., Lange-Bertalot, H., Metzeltin, D. & al. - Lake Baikal: Hotspot of endemic diatoms I. in Taxonomy - biogeography - diversity. 23. (http://api.cybertaxonomy.org/phycobank/app/registration#!workingset/5d29277e-a527-4a26-8685-1a7a6cb2e3de) fails on the production server due to excessive heap consumption after pressing the save button in the name editor.
The problem happens after the name is saved during the reloading of the workingset:
A differential comparison of the heap before and during the reloading of the workingset shows that especially the amount Team objects is increasing excessively.
1 minute after saving +25.000 Team objects
3 minutes after saving +109.000 Team objects
Comparing the objects in memory from 3 minutes and 1 minute after saving reveals that only the amount of Team objects is increasing that much!
The allocation analysis shows that all Team Objects have been created in the call to the RegistrationWorkinsetService
There are 423 Teams in the database but in the test above more than 100.000 Team objects have been created evene after 3 minutes.
Files
| stacktrace.png (99.8 KB) stacktrace.png | |||
| mem-diff-2.png (47.2 KB) mem-diff-2.png | |||
| mem-diff-1.png (52.7 KB) mem-diff-1.png | |||
| mem-diff-1-2.png (45.7 KB) mem-diff-1-2.png | |||
| Allocations-of-Teams.png (92.9 KB) Allocations-of-Teams.png | |||
| mem-getCollectorAndFieldNumber.png (33.5 KB) mem-getCollectorAndFieldNumber.png | |||
| mem-getCollectorAndFieldNumberXX.png (20.1 KB) mem-getCollectorAndFieldNumberXX.png |
Related issues
