[quote=UnixMover]The app finally died during a 19.5k run (note it took 4 days before it died). I then implemented the Sun recommendations for the JAVA engine however to no avail, the system died during a 18k data run.
[/quote]
That does sound very slow, what do you have heap set to and what other modifications are you making.
Yes, but the majority of the memory is held onto by the metadata in the files. i.e if you just load 20,000 songs into Jaikoz (and do nothing else) that will use alot more memory than if you load 5,000 songs.
More memory is used when you autocorrect, but most of that should be freed once the autocorrect has completed. Saving changes means that there is no difference in the metadata in the song on disk and the song in Jaikoz, that will freeup some more memory, however to reiterate the majority of the memory is used up loading songs into Jaikoz
Im well aware of this problem and have a solution to do this, essentially alll the metadata for your loaded songs will be held in database, and only the subset currently displayed will need to be held in memory. but this is
a major change that I am having to implement outside of Jaikoz and then merge back in when I am happy with it.
You need to increase your max heap, you can see what this is set to in Jaikoz by looking the first line in the Jaikoz console, the default value is approx 800 mb.
It is rather difficult for a Java program to get a comprehensive view of the security setup on Windows, but the situation improves somewhat with Java 7. Id need to see the log files to find out if there are cases where Jaikoz is unable to write when it should be able to write but you may be encountering the following:
Sometimes Jaikoz has to create a new file in a folder, write to that file and delete your original file rather than just write directly to your file. So for that reason you need permissions to create files in the parent folder rather than just be able to edit the files. Whether or not this is required depends upon whether the original file has a metadata tag large enough for the new metadata, and the audio format you are writing to.
Would be keen to see the stack trace of this exception, should be in Jaikozdebug0-0.log