keeps/roda-in

Removing packages from RODA-In after SIP creation causes freeze

MSavels opened this issue · 5 comments

MSavels commented

To test RODA-In (v2.3.0), I created a couple of SIPs with some tens of files and about 100MB of data. After SIP creation, I tried to remove the data from the middle part of the RODA-In window (2. Information Packages), but this caused strange behaviour. The window started jittering, as if it was continuously switching between active and inactive and RODA-In became unresponsive. After a while, my system crashed due to a memory overflow issue. I tried to recreate the behaviour in the same way, and that worked, only now, the system did not crash, but RODA-In remained unresponsive. Checking the control panel revealed that the OpenJDK Platform / RODA-In was eating up in excess of 2 GB of RAM. A forced shutdown of RODA-In released the memory.

I am using an older system, though, so that could be the cause:
Intel Core i7 - 4770@3.40GHz (x64)
Windows 8.1 Pro (64 bit)
8.00 GB of RAM
Java version 1.8.0_251

luis100 commented

To reset RODA-in please use the menu option File > New project.
To diagnose the issue we would need the log file. Try the menu option File > Open configuration folder, find the log folder and check if the roda-in.log file has information pertaining to this crash that you can share.

MSavels commented

There is a log file from the time of the crash. It does not appear to hold relevant information, but I will send it to you anyway. I will not share it here, but I will e-mail it to you.

luis100 commented

The log file doesn't show any clue. We will try to replicate the behaviour based on your description, but if that is not possible we will need more information to be able to find any memory leak.

JelleKleevensVAI commented

To replicate this issue:

  1. New classification scheme > add new node
  2. Associate data with "One classification scheme from folder structure"
    image
  3. Remove top node.

--> memory leak

luis100 commented

@JelleKleevensVAI I confirm the steps allow to replicate the issue, the application freezes, although I don't think the issue is a memory leak, but instead the application seems to get into an infinite cycle.