Weird Bug with MM Skin

EliteXen · Post by **EliteXen** » Wed Apr 11, 2007 1:00 am

I haven't been able to figure out a pattern to it, but it seems occassionally MM's player loses all of the skinning. MM is still functional, just can't really access the controls.

The closest i've come to finding a pattern to the behavior is that it tends to occur if I do a lot of rating/tagging ie play song for few secs, change the rating, then play next song.

Anyone else ever notice this?

Edit:
I'm running Vista Ultimate and this has happened with all 3 alpha builds.
I also noticed something similiar occuring with the MM2 player back on XP. The song name would stop scrolling and the player controls would become unresponsive, but the skinning never completely disappeared like this. Also it occassionally would automatically resolve itself with MM2. Currently on MM3 I have to exit MM before the skinning returns. Closing it to the system tray doesn't help.

junglemonkey · Post by **junglemonkey** » Wed Apr 11, 2007 3:40 am

i have seen this before in mm 2 and mm 3 it is system resources.
it seems monkey needs to use a lot of them when doing lots of editing so it will tend to make windows clear the system resouces which is were the images are also held for the skin when you use monkey.
best thing to do is change the size of the page file in xp virt mem in win9x don't know what it is called in vista?
make it about one eighth the size of the hard drive.
also make sure you have a lot of ram for use.
i know xp uses a min of 160mbs just for its own operations
i don't know what vista os' needs.
but it is atleast that much. so get as much as your mother board can hold and your os's can handle or that you can afford.

find a ram cleaner that will work on your os and get it don't buy it if you can find a free one that works if not then you have to buy one. the ram cleaners are more well behaved they only clean out the unneeded or unused files that are still in the ram or resources. when windows does it they don't care they take out a certain amount and don't care if it was being used or not.

that should fix the image troubles but if not then if mm3 wants to send a bug report in let it. cause you are on vista and that is not yet fully supported so your one of the scouts for that.

EliteXen · Post by **EliteXen** » Wed Apr 11, 2007 10:46 am

junglemonkey wrote:i have seen this before in mm 2 and mm 3 it is system resources.
it seems monkey needs to use a lot of them when doing lots of editing so it will tend to make windows clear the system resouces which is were the images are also held for the skin when you use monkey.
best thing to do is change the size of the page file in xp virt mem in win9x don't know what it is called in vista?
make it about one eighth the size of the hard drive.
also make sure you have a lot of ram for use.
i know xp uses a min of 160mbs just for its own operations
i don't know what vista os' needs.
but it is atleast that much. so get as much as your mother board can hold and your os's can handle or that you can afford.

find a ram cleaner that will work on your os and get it don't buy it if you can find a free one that works if not then you have to buy one. the ram cleaners are more well behaved they only clean out the unneeded or unused files that are still in the ram or resources. when windows does it they don't care they take out a certain amount and don't care if it was being used or not.

that should fix the image troubles but if not then if mm3 wants to send a bug report in let it. cause you are on vista and that is not yet fully supported so your one of the scouts for that.

I have 3gb of mem and my pagefile is set to 5gb. I've seen this happen when my system is basically idle (fresh after a restart) and using less than 500mb or mem so I'm sure it's not running REALLY running low on resources.

rovingcowboy · Post by **rovingcowboy** » Wed Apr 11, 2007 12:34 pm

well thats strange.?
becuse that is what it was on my win98 and winXp. i adjusted
them and it fixed that stuff.

must be something else throwing it for a loop on the vista?

Steegy · Post by **Steegy** » Wed Apr 11, 2007 12:39 pm

I think this is the same problem I sometimes notice on MM 2.5.5. Sometimes, if a song is playing and I am editing its tags in the track list (the edit textbox is visible) and then double-click another track to let it start playing, MediaMonkey's player crashes (Access Violation at address 00000000. Read of address 00000000).
MediaMonkey itself is still running, bur certain commands always give a(nother) access violation, and if I close MediaMonkey, it keeps on running in the background.

Maybe depending on the MediaMonkey/Windows version and protection settings (like DEP), the problem can give different results.

I never reported this problem because I never checked it out on a new version (MM2 is still 2.5.5.988).

Addition: 2 debug logs (MM2 and MM3) have been mailed to the devs.

junglemonkey · Post by **junglemonkey** » Wed Apr 11, 2007 4:58 pm

there is a brand new just released today driver
that might help here is the info from the link at
http://www.majorgeeks.com

Intel Graphics Accelerator Driver for Vista 15.2.3 [ 15.7 Mb | Freeware | Vista]
Vista drivers for most Intel Express Chipsets.

Steegy · Post by **Steegy** » Wed Apr 11, 2007 6:02 pm

This doesn't have much to do with graphics, and certainly not with Vista. I think it's just a plain MM bug.

Morten · Post by **Morten** » Wed Apr 11, 2007 6:10 pm

Yep it is.

EliteXen · Post by **EliteXen** » Wed Apr 11, 2007 8:56 pm

Yah I figured. It's kinda weird that it carried over from MM2 to MM3 with the amount of rewriting they did.

If any of the devs see this let me know what information you need me to send. Hopefully we can get it resolved.

EliteXen · Post by **EliteXen** » Thu Jun 21, 2007 5:37 pm

EliteXen wrote:Yah I figured. It's kinda weird that it carried over from MM2 to MM3 with the amount of rewriting they did.

If any of the devs see this let me know what information you need me to send. Hopefully we can get it resolved.

Still having this issue in MMA5, though it's pretty rare it's extremely frustrating. Can a dev at least comment on this. I'd be happy just knowing that the problem is documented on their To Do list, but it doesn't have to be any time in the near future.

Post by **jiri** » Fri Jun 22, 2007 8:48 am

We would be certainly interested in as many information as possible, i.e. a debug log and a description of how/when the problem occured.

Jiri