I don’t think the RAM size is too small or the file size too big, but it is difficult to say what the reason then is for the frequent crashes. Unfortunately we have several reports of hard crashes on Windows that are so far not understood.
There might be useful information in following log files on mentioned PC:
in ELAN’s installation folder, there might be crash logs with names like this hs_err_pidnnn.log
Maybe there are messages in those files that give you an idea of the cause of the crashes, if not, you’re welcome to send those files to me (han.sloetjes AT mpi.nl) for inspection.
Sorry for the late reply, I did not notice that I disabled the notifications. I have sent you those files for inspection.
The files labeled as hs_err_pidnnn.log. I do not know if this is relevant at all, but they were not saved in the installation, but they showed up in a folder where my collaborator stored the video file and the translation that he was working on.
Good morning.
I am experiencing something similar (Windows 10, 8 GB RAM, 237 GB memory). I work with several files and it seems to happen with any of them. The heaviest is 1.45 GB (20 minutes), but it seems to happen also with other that are smaller (around 100 MG).
Do you think it is related to file size?
Thank you very much
Eleonora
Hello,
I don’t think the size of the video file is the problem and in case of the 100 Mb file I’m quite sure the size isn’t the problem.
Do you, apart from the video file, also have a .wav file as one of the linked files? If not, did you hide/remove the Spectrogram and Signal viewer via the View->Viewer menu?
If you haven’t tried that yet, maybe you could do so, to see if that makes a difference? We’re not sure yet, but we have indications that the extraction of audio samples from the video has some memory related issues.
Just as another data point, I was having a similar issue where ELAN was stuck on initializing when opening files with .wav audio and multiple video files. For the moment, hiding the spectrogram and the wav form seems to have fixed the issue. Thanks for this thread!