SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

How to disable memory errors?

#1

I just purchased today jaikoz audio tagger v1.11.2 It is a great program but I am constantly getting errors that are really frustrating me. I have been running Jaikoz on both my winxp and win03 machine, both have 2gb of ram.

I have a collection of 25k files I am trying to clean up. I have them divided by alpha and numeric, so my folders range anywhere from 500 to about 2k files. When I try to load a folder, it loads very quickly. I then hide all the fields I do not want to modify and select all the visible fields to delete which I do by right clicking and choosing Delete. Half the time it will take about 10 seconds then complete and I can then save the files, the other half of the time it will up with an error stating “Out of memory, Jaikoz must be restarted, to increase the memory allocated to jaikoz modify its memory settings in the start up file and then restart.”

The system can handle these file rewrites fairly easily, especially since all my folders have been broken down so that I am not trying to convert all 25k at once. Is there anyway I can turn off this check, or not limit the amount of ram it thinks i can only use?

Also I noticed the batch file and I modified those numbers in there of both the xms and xmx and that didnt see to make much difference. I also noticed there was a bunch of other parimeters that the batch file called. Is there a list of what modifiers we could use on the exe file?

The other thing that I am wondering is there is a save settings option, but iI can not tell what settings it is saving. Is there anyway once i get my edit tab looking the way I want it with some fields showing and some not showing to save that view so that it shows that way every time i bring up the app?

Please help. The random 2 out of 3 crashes I get per attempt to clean up files is driving me bonkers.

#2

[quote=greengeek] I then hide all the fields I do not want to modify and select all the visible fields to delete which I do by right clicking and choosing Delete. Half the time it will take about 10 seconds then complete and I can then save the files, the other half of the time it will up with an error stating “Out of memory, Jaikoz must be restarted, to increase the memory allocated to jaikoz modify its memory settings in the start up file and then restart.”
[/quote]
This doesn’t sound like it really is a memory error, there may be a different underlying cause, please send me your jaikozuser0-0.log and jaikozdebug0-0.log so I can investigate further.

Unfortunately with Java you have to set a maximum memory heap size, you cant just set it to unlimited. If it really is a memory problem increasing these numbers should make a difference, however editing the batch file will only have an effect if you run Jaikoz.bat. If you run Jaikoz.exe you need to edit the

lax.nl.java.option.java.heap.size.initial=67108864
lax.nl.java.option.java.heap.size.max=256000000

fields in jaikoz.lax instead, by default it is set to mimimum heap size of 64Mb and maximum of 256Mb, so you could increase the second figure to 1000000000

allowing heap size of upto 1GB

Once again, if using the exe file you need to modify a value in Jaikoz.lax
rather than the batch file.

lax.command.line.args=-l2 -m2 -f

In either case these other parameters refer to logging

-l outputs information in Jaikoz, so this is concerned with the various tasks that can be performed in Jaikoz.

-m outputs information in the the jaudiotagger library, so this is concerned with the reading and writing of files.

Both accept values of 1-7, the higher the value the more output will be generated, if you set to higher than 4 jaikoz will slow down noticeably in some circumstances.

-f ensures the debugging in written to the jaikozdebug.log file

Yes, just moving columns around in the diaply does not automtically restore them on next invocation of Jaikoz. You need to go to ‘Settings/Table Settings’ menu item to define the columsn that should be displayed by default on startup, you can use ‘From Display’ button to use the existing setup as the default.

The ‘File/Save Settings’ menu item will then tave ANY settings/preferences you have made during this session of Jaikoz.

#3

Thank you,

I emailed the requested log files to support@jthink.net

I made the changes to the batch file and was running the program from it and was still recieveing those errors. I havent yet modified the java files themselves, but can try that as well.

Thanks for you help.

#4

I can’t figure out why it thinks it is out of memory when I keep getting these errors. The task manager is not showing any large amounts of system resources being used nor am I seeing any slowness on the system. It also seems to be somewhat random, though I typically get these errors 4 out of 5 tries. I can do 900 files then try 400 files the next run and the 400 files will error out.

#5

[quote]lax.nl.java.option.java.heap.size.initial=67108864
lax.nl.java.option.java.heap.size.max=256000000

fields in jaikoz.lax instead, by default it is set to mimimum heap size of 64Mb and maximum of 256Mb, so you could increase the second figure to 1000000000

allowing heap size of upto 1GB [/quote]

I made these modifications and it did not change anything. It still is reporting the same error and shutting down the program. It appears that it is reporting this error prematurely and shutting down the program with out cause as I am still not seeing any hit on system resources, including memory to anywhere even close to the ammount we have set in the file.

#6

Hi, Ive taken a look at the logs. I dont know how technical you are but the problem is that every field you delete is processed seperately, and if the field you delete is in the Artist,Album or Genre column then the data has to be reindexed in a separate thread to make sure the Browser is synced with the data, it is running out of memory generating threads. I need to change the way of doing this so it works better when you modify many fields, however I was not expecting so many fields to be deleted in one go.

In your log file you load 4,643 files but then delete 264,651 fields in one go, I assume you are basically blanking out all the fields ?

#7

That is correct. I find that your program is the best for displaying what is in those fields and clearing them out.

Is there an easier or better way of doing this? Basically clearing out all content out of all fields, other than a handful of fields like album, title, artist, artwork? Even if it is something as ugly as running a command line script?

#8

Yes, what you could do is:

Load your files
Change the Version field of the first record to ID3v1
Copy and paste this value to all other rows
Then do ‘File/Force Save’ menu item

this will save all your files to ID3v1 format, ID3v1 can only hold album, artist, title, track no, genre, comment so everything else will get lost.

If you reopen your files the version will be set to ID3v23 by default (See ‘Settings/Save Settings/ID3 Tag V2 Tab’ menu item) so if you now start adding extra info this will be saved on a subsequent save.

#9

The problem with deleting many fields in one go is fixed in Jaikoz 1.12 release today.

#10

I downloaded the latest version a month or to ago and was trying it out and it worked great. I didn’t get a single memory error. I have been meaning to get back and update this post, but been busy tagging =)

The software is working great! Keep up the awesome job!!!