bug #7900

Updated by Andreas Kohlbecker 9 months ago

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.* (!workingset/5d29277e-a527-4a26-8685-1a7a6cb2e3de) fails on the production server due to excessive heap consumption consuptions 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`

![(Allocations of Teams - fist number in Table is the object count](Allocations-of-Teams.png)

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.


Add picture from clipboard (Maximum size: 40 MB)