INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: michel on February 17, 2003, 03:22:27 am
-
except if you have a very large amount of memory. I have 196MB of memory and 256MB of virtual memory (swap file) running under win2K and I cannot tag more than a few thousands of files without to get a "virtual memory low" message and finaly MC crashes.
So I cannot tag all my library (23000+ files), I have to split in small parts of about 3000 or 4000 files.
I am not sure it is memory leak, it is may be due to the undo capabilities of MC. Anyway it is a problem because when MC crashes the result are inconsistencies between the files and the database.
-
it also could be OS related
-
Probably not...the mem leak issue seems to have reappeared from what I've seen in other posts...can't remember where though!
-
Just a point - that's a pretty low amount of memory.
That's the size of your swap file you mean right??
Mine's around a gig. You should let windows manage it or if it does a bad job managing it then you should set it to something high if you have the spare space as the only down side of making it extra big is loss of space.
-
If you watch Task Manager, can you see where it leaks?
Can you isolate it at all -- tag creation, tag removal, ID3v1 vs ID3v2, etc.
Thanks for any help.
-
If you watch Task Manager, can you see where it leaks?
Can you isolate it at all -- tag creation, tag removal, ID3v1 vs ID3v2, etc.
Any tag operation, it seems. For example, I select all files (ogg, mpc ape tag, mp3 id3v2), and then I request a move field A to field B (but it is the same for older tag operations). Progressively it takes more and more memory until to crashes ("low virtual memory" warning before).
It seems that it is not a permanent memory leak because I can apply consecutive tag operations on about 4000 files selected, without to exit MC, and then there is no problem.
-
Turn off "Update tags when file info changes" in Options -> General and let us know if it still leaks.
Need to know if it's the tagging or something in MC.
Thanks!
-
Turn off "Update tags when file info changes" in Options -> General and let us know if it still leaks.
I just tried it: MC starts with 24MB and finishes with 30MB, so there is no real problem without updating the tags.
-
Can you isolate it to certain formats?
MPC, APE, MP3, etc.?
If it's MP3 (my guess), what happens if you turn off "Ignore ID3v2" in the MP3 plugin's options. (in Plugin Manager)
Thanks for troubleshooting this!
-
Can you isolate it to certain formats?
MPC, APE, MP3, etc.?
If it's MP3 (my guess), what happens if you turn off "Ignore ID3v2" in the MP3 plugin's options. (in Plugin Manager)
It was off already so I set "ignore id3v2" and I am trying a mass tagging (adding a value to compser field). MC started with 20MB of memory and it is ising 50MB after to tag about 1000 files...
I don't like to much to do that because there is no 'cancel' buttom so MC crashes before to finish when it doesn't have memory anymore and I can have an audio file corrupted may be.
PS. I don't understand: you don't have a bunch of mp3 files at JRiver ?
(I use only id3v2, not id3v1, and also mpc-ape and ogg)
-
It is may be 'file type related' because the memory leak is not "linear"
MC is using 50MB after to tag 1000 files (starting at 20MB)
now MC is using 60 MB after to tag 2000 files...
-
No, we don't have MP3's here. Just bread, water, and some computers. I had an AM radio once, but Jim took it away.
Seriously, we keep trying to reproduce the leak, but we can't. That's why I'm asking for help.
Does the "Don't save" for either ID3v1 or ID3v2 make a difference?
Thanks for everything.
-
Does the "Don't save" for either ID3v1 or ID3v2 make a difference?
I cannot do 2 tests in the same time ! The previous one with ""ignore id3v2 during analysis" set is not finished yet (remember: I have 23000 files and a PII 350...).
Right now: about 70MB after 5000 files tagged.
PS. Could be possible to have a 'cancel' buttom for tagging operation ?
-
80GB after to tag 6000 files.
I will stop now killing MC otherwise I would wait a long time to finish that.
Sometimes the amount of memory used decreases before to increase again.
-
I am testing with only ogg files now (2700 files). Memory usage is continually increasing (about 100KB every second).
-
As far I can see MC leaks about 110K for each ogg files tagged (it is adding a 'performer' tag).
-
MC 115 continues having memory leak during file tagging (I just test doing "update tag from library") except may be for mpc files (with ape v2 tagging).
For both ogg and mp3 (id3v2) files, memory usage increases for each file tagged, may be faster for ogg files.
All my cover art are "inside".
-
OGG should be fixed in 9.0.116.
MP3 should be fixed in one of the coming builds.
Thanks for all your help.