Upload Archive Memory bug #13
Description
Describe the bug
When doing an upload of an archive the RAM that is needed to analyse the archive doesn't get freed after the analysis has finished.
To Reproduce
Steps to reproduce the behaviour:
- Go to '/product/[id]/view'
- Click on 'Upload'
- Choose File (Upload a BOM (CSV, XML) or archive file format (ZIP, TAR, WAR..))
- Click 'Upload'
- After the Upload process is finished the memory is not freed
Expected behaviour
After the Upload process is finished the memory should be freed
Additional context
The classes for processing an archive were mostly rewritten and optimized. The old implementation contained a few errors. The rewrite has partially improved the memory problems, but not completely.
Also, the problem was that previously several different uploads were mixed together, which is not allowed to happen under any circumstances. I have not tested this again until now to see if this is now fixed.
Uploads of archives should therefore still be treated with caution and after each upload, it is best to restart the container to free up memory.
The uploaded archive still takes up memory space after the upload has been processed. It's less than before but still not good enough.
A deeper analysis of the garbage collector needs to be done.