Matt, et. al. -
After some further experimentation, it appears that my MC 18 memory problems are related to a combination of Theater View, Display View and use of the visualization options, specifically 3rd party add-ins from Soundspectrum, G-Force and Winter Wonders.
The significant memory leak I observed initially appears to have been related to using Soundspectrum's Winter Wonders 2013 visualization within MC 18. When using this visualization in Theater View/Display View, MC 18's memory use grew from 135MB to 900MB over about 12 hours. Please note that this leak does not occur with MC 16, even when using the Winter Wonders plug-in in the same way.
Using the G-Force visualizer seems to result in a much smaller, but still measurable, growth in memory use. When using MC 18 in Standard View with the cover art visualization, memory usage was stable at approximately 30MB for several hours (with music playing). Switching the visualization option to G-Force caused the memory footprint to jump immediately to 62MB, but again it stayed stable at or near that value for several hours. Switching to Display View (from within Standard View) caused another jump to about 84MB, but again the memory use stayed at or near that value for several hours. Next, I switched to Theater View, then selected Display View from within Theater View (still with G-Force visualization). Memory jumped immediately to 148MB. Over about 12 hours, that value grew to 230MB. Again, using MC 16 this increase in memory use is not observed.
So, it appears something is going on with the way MC 18 interacts with 3rd party visualizers in Theater View/Display View. I am going to have to revert to MC 16 until/unless this problem is found and corrected. I understand that this may be difficult/impossible due to more than one company's SW being involved. Please let me know if there is more troubleshooting information I can provide, and Happy New Year to all...
Jim Logan
31 December 2012