INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: graham131 on February 24, 2003, 02:18:05 am
-
2 problems / bugs. Both are related.
I have a library of approx 31,000 tracks.
1st Issue
If i do a CTRL A to select all then right click and select Analyse Audio, my prcessor utilisation goes to 100% for about 6 or 7 mins, MJ says not responding in Task Manager and my PC grinds to a snails pace. If I am patient it will eventually process the information and bring up the analyse audio dialog box.
At that point I hit analyse,
Same thing then happens - 100% processor for 5 or 6 mins, MJ not responding etc.
Wait patiently then Audio Analysis begins. Processor runs at about 23%, Memory usage between 170 and 230Mb.
PS Nothing else is running while i am doing this.
Second Issue
After an inderminate period of time - sometimes an hour, sometimes 5 hours, the memory leaks - whoosh up to 2.13 GB in use - Windows starts allocating Virtual Memory etc and increasing sizes. At this time the CPU utilization is then back up to 100% also. Media Jukebox is also shown as "not responding" in Task Manager.
Media Center then reports "error" in the Audio Analysis window for tracks, then stops / hangs completely.
Memory is still "off the scale"
If i then click "stop" and wait the customary 5 or 6 mins for MC to refresh I get emphasis back.
Memory and CPU utilisation is still high.
I click to exit Media Center....
Program ends.....
Memory usage drops to sub 100Mb
CPU Utilisation drops to 2 or 3 %
All is ok.
I can then restart MC and repeat.... (PS even if i reboot / switch off i can recreate it)
If i pick less files at a time ie 1500 the same happens however the times for processing are obviously reduced.
System Information is posted below.
Hope you can help
Graham ;D
Media Center Registered 9.0.119 -- C:\Program Files\J River\Media Jukebox\
Microsoft Windows XP Workstation 5.1 Service Pack 1 (Build 2600)
Intel Pentium 4 2538 MHz MMX / Memory: Total - 1048 MB, Free - 796 MB
Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1106 (xpsp1.020828-1920)
Shell32.dll: 6.00.2800.1145 (xpsp2.021108-1929) / wnaspi32.dll: Internal ASPI Layer
Ripping / Drive E: Copy mode:ModeBurstBigBuffer CD Type:Auto Read speed:Max
Drive F: Copy mode:ModeBurstBigBuffer CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: No
Burning / Drive F: YAMAHA CRW2200S Addr: 0:2:0 Speed:20 MaxSpeed:20 Use MJ Engine:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: No / Normalization: None
-
Same problem here. This issue was also present in version 8 as well and all of the version 9 builds. I just finished analyzing all of my files yesterday but did them in groups of 500 or less.
Carl
-
I've noticed the same... Soon I won't be able to use MC on a 400mhz Pentium II, 256 mb RAM :( Guess that's progress... On the other hand I still keep coming back to MC because it's such a great product...
-
Problem 1
This will be almost instant next build. There were two slowdowns -- both of which will be optimized away.
Problem 2
We've heard a lot of reports of this but can't reproduce it. We'll keep digging.
-
Problem 1
This will be almost instant next build. There were two slowdowns -- both of which will be optimized away.
Problem 2
We've heard a lot of reports of this but can't reproduce it. We'll keep digging.
Problem 1 - wow yes this is instant sort of!
The initial "If i do a CTRL A to select all then right click and select Analyse Audio, my prcessor utilisation goes to 100% for about 6 or 7 mins, MJ says not responding in Task Manager and my PC grinds to a snails pace. If I am patient it will eventually process the information and bring up the analyse audio dialog box." - Is fixed and instant
The second part of problem 1 - "At that point I hit analyse, Same thing then happens - 100% processor for 5 or 6 mins, MJ not responding etc. Wait patiently then Audio Analysis begins. Processor runs at about 23%, Memory usage between 170 and 230Mb. " - Is better - it now takes 3 mins!!! - but not fixed
The "second issue" - i can recreate everytime. What i cannot do is tell you the exact time / reason for the leak as this varies. My latest Audio Analysis lasted just over 26 hours (14:00 yesterday to 16:20 today) before failing. In that time is managed 7000 tracks.
I still have approx 16,000 to Analysis.
Cheers
GRaham
Anything you wan t me to try please ask.
Thanks
-
Matt,
Memory leak actually seems much worse in .320. I am able to recreate it very quickly selecting in excess of 2000 tracks. It fails almost immediately with errors in the Analyse Audio window, with a corresponding exponential curve with memory until it just fills everything and hangs.
Hope this is of benefit?
Graham
-
Try doing a single type of file (mp3, for example).
It would help to have another clue to find this.
-
Try doing a single type of file (mp3, for example).
It would help to have another clue to find this.
Jim, I am now running (as I type) 1,999 MP3 files only. It has started (so as immortalised by so many) , lets see whether it finishes.
If this works I will try more than 2000
I will also sort by type. My vast majority of files are MP3 but I must admit I am gettin partial to Ogg.....
Thanks
Graham
Update - 36 from 1999 completed - all ok
-
Update:
I left it running when I went to bed. When i got up there were still 376 files queued, the Momory had leaked to over 2Gb, I had a Windows Virtual Memory Varning flashing and MC had stopped functioning.
Pressed "Stop", waited a few secs, MC regained Emphasis, Memory still high.
Exited MC - 5 secs later memory usage falls to 137Mg, Windows refreshes Virtual Memory - All OK
What shall I try next?
System Properties below
Media Center Registered 9.0.120 -- C:\Program Files\J River\Media Jukebox\
Microsoft Windows XP Workstation 5.1 Service Pack 1 (Build 2600)
Intel Pentium 4 2537 MHz MMX / Memory: Total - 1048 MB, Free - 765 MB
Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1106 (xpsp1.020828-1920)
Shell32.dll: 6.00.2800.1145 (xpsp2.021108-1929) / wnaspi32.dll: Internal ASPI Layer
Ripping / Drive E: Copy mode:ModeBurstBigBuffer CD Type:Auto Read speed:Max
Drive F: Copy mode:ModeBurstBigBuffer CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: No
Burning / Drive F: YAMAHA CRW2200S Addr: 0:2:0 Speed:20 MaxSpeed:20 Use MJ Engine:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: No / Normalization: None
-
Graham,
I'll try it tonight with my 5000+ files to see if I can see the same.
One thing you could try is fire up Windows TaskManager, go to processes, hit the View menu item then Select columns and click on "Virtual memory Size" and "Peak Mem Usage".
Then just fire off an analyse with just 300 files taking a note of the memory use before you start and every 10 files. That will definately prove that MC is not releasing memory somewhere along the lines and that it's on a per file basis.
-
I'm currently trying 3000 files (mp3's), watching memory closely...Analyze audio window came up fast, analysis started up fast..so far about 20 files in, memory is stable.
update- 500 files, RAM has flickered +/- 3M...very stable.
2nd update- Done. Only odd thing that happened was after adding songs to playing now during the analysis, RAM went up 10MB instantly, then climbed another 10MB in the second half of analysis.
-
I have been trying batches of less then 500 now , all day. I am on my 3rd batch - So far so good.
-
UPDATE:
4th Batch of files - 496 files has just failed with 63 to go. Massive memory leak.
Interesting though - the few files that seem to have been analysed before it failed were reporting -157Db
Odd
Anyway, I will carry on
-
Very interesting ... what happens if you analyse just those last few files?
Maybe the issue is file related in that it's slightly corrupt or contains data not expected by MC?
As an update I have just kicked off my analyse and it's done 100 here so far with no problems.
-
I had a few odd values in .119, some files that skipped the analysis for no apparent reason did fine the second try, and some others returned weird values that were corrected the second go around. In .120, no problems so far, seems solid here.
Media Center Registered 9.0.120 -- C:\Program Files\J River\Media Jukebox\
Microsoft Windows XP Workstation 5.1 (Build 2600)
Intel Pentium III 600 MHz MMX / Memory: Total - 261 MB, Free - 107 MB
Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpclient.010817-1148 ) / Shlwapi.dll: 6.00.2800.1106
Shell32.dll: 6.00.2600.0000 (xpclient.010817-1148 ) / wnaspi32.dll: Internal ASPI Layer
Ripping / Drive H: Copy mode:ModeBurstBigBuffer CD Type:Auto Read speed:Max
Drive I: Copy mode:ModeBurstBigBuffer CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: No
Burning / Drive I: MITSUMI CR-48X8TE Addr: 1:1:0 Speed:16 MaxSpeed:16 Use MJ Engine:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: No
Use playback settings: No / Normalization: None
-
400 files so far and no major fluctuations in memory usage.
-
Just to let you all know.
I have been fighting this memory leak for some time now.
At this moment I am analyzing over 3000 mp3 files to see what happens. I am using build 9.0.120 on XP home
Let you know what comes out ...
Peter
-
I just stopped the analysis after 1400 files.
It was still stable!!!
Peter
-
Stable here after 2000 files ... I defo recon it's a corrupt file.
-
I guess it is a corrupt file in combination with bulk analyses.
This time it crashed after 1000 files or so.
The strange thing is that after a restart it does the analyses as if nothing happened??!!
To me it remains a ghost.
As soon as i have more details I will start a new thread.
Peter
-
Ok here's something, maybe someone can check this out on their end.
I had an Analyze Audio "freak out" with weird values (error listings instead of analysis, 0 BPM's, very low %, and millisecond analysis on some 7min songs) and the RAM skyrocketed...
I found a common value in these files though, all the file names had underscores in them. Any single word song or songs in which the underscore was replaced with spaces did fine. Anyone care to test this, see if I'm nuts (ok, I'm nuts anyway ;D, but seriously, see what you get)