Using:
jamdb-0.9.9
DBI-1.53
DBD-mysql-4.00
mysql-5.0.26
On a clean install, running 'jamdb -u' all seems to go well until around the 1600th file has been added to the database, then...
AAdd: /data_lan/mp3_2/Electronica/Eskimo/Take_a_Look_Out_There/Eskimo_-_07_-_Survive_Your_Dreams.mp3
/data_lan/mp3_2/Electronica/Eskimo/Take_a_Look_Out_There/Eskimo_-_08_-_Time_Becomes_a_Loop.mp3: changed track from 08/09 to 08
adding 'Eskimo': 'Take a Look Out There': 'Time Becomes a Loop' ...
AAdd: /data_lan/mp3_2/Electronica/Eskimo/Take_a_Look_Out_There/Eskimo_-_08_-_Time_Becomes_a_Loop.mp3
Out of memory!
A subsequent re-run of 'jamdb -u' throws the following error...
# jamdb -u
building comparison lists ...
searching directory /data_lan/mp3_2/ for files ...
searching directory /mp3 for files ...
12007 files found on disk
1599 files found in database
searching for new files ...
searching for deleted files ...
Out of memory!
I'm almost certain that this is something very simple to do with the way JamDB's queries are handled with MySQL5.
I would have liked to keep using MySQL4 but unfortunately it throws the error 'Transactions not supported by database' due to a bug in the handling of $dbh->{AutoCommit} = 0;
This is fixed in subsequent upgrades of MySQL, DBI and DBD-MySQL, but the memory error now appears.
Marc, it would be hugely appreciated if you could release a maintenance version, even just to bring it up to current software dependencies.
Cheers,
Rick 8^)
BTW, outstanding job - been using this software since 2002
Logged In: YES
user_id=633121
Originator: NO
Hi Rick,
thanks for the report! Have you tried to find out if a special file (maybe broken) is causing this? Perhaps ehose Eskimo files are broken somehow?
We have no clue ATM what would cause this.. :-/
But as soon as we have a solution I will release a maintenance version.
Cheers
-Marc