En-Mass Errors

Teknojnky · Post by **Teknojnky** » Tue Jan 17, 2006 7:01 pm

An option for "save settings NOW" would be nice..

hmm, wish list...

rovingcowboy · Post by **rovingcowboy** » Wed Jan 18, 2006 10:59 pm

their right that is a feature not an error it was a slip of the mind that made me call it an error for i remember that might have been added as a feature to stop or trying to stop the song from jumping back to the front when editing the current playing song's propeties.

by the way it did not work? the songs still jump.

rovingcowboy · Post by **rovingcowboy** » Wed Jan 18, 2006 11:06 pm

okay jiri believes the errors listed here with the canvas does not allow drawing and the persistant now playing window are caused by lack of resources.

since monkey does those errors when i have only the explore and the system tray and monkey running either windows explorer is causing the memory leak that is eating the resources or the system tray is, or the monkey himself is.

i have confirmed there is a memory leak that might be causing all the errors just where the memory leak is at is not known by me just that after playing monkey for some time it does bog the system down enough to not allow right clicking on the album art. and to cause other things to take time to load like the options for monkey.

this memory leak is also not large as it does not set my ram cleaner off. it is just a slow memory leak that takes atleast 6 to 8 hours of playing monkey to show up.

i do run pekes scripts all the time.

so the script area of monkey might be the cause of the memory leak.

can anyone else with these error's find any symptoms of a memory leak on their computers. since it is a slow leak the only computers that seem to be effected by it are the slower cpu ones.

rovingcowboy · Post by **rovingcowboy** » Thu Jan 19, 2006 11:12 pm

I've been checking this memory leak thing all day. and i have come to the conclusion that it is not the script area of monkey. but it seems to have something to do with how monkey is connecting to the windows explorer shell?

Why do i think that?

well i can start programs all day long with it and the memory leak does not grow faster because of my opening up other programs.

but when monkey is started it works fine but the longer it stays running the more sluggish it becomes and then around 10 to 12 hours of use it toss's the error for not allowing me to right click and get a context menu for the album art. then the error for the now playing window shows up.

and if i start editing songs i get maybe 4 to 9 songs and the canvas does not allow drawing shows up.

but if i start monkey and go in to all the leveling and editing and moving around with auto organizer i can get around 10 to 20 songs done before it toss's the error for the canvas does not allow drawing.

so it seems to be in the shell connection area of monkey someplace?

atleast that is what it looks like to me but read my sig

rovingcowboy · Post by **rovingcowboy** » Fri Jan 20, 2006 1:41 pm

sorry for so many posts with nobody else replying in between them.

but i keep getting more info on these.

it seems the memory leak is dealing with editing of album art or just the changing of the album art in the viewer window.

not sure which it is but it gets worse faster when it changes lots of album covers. something i did not do until i started testing that feature. then i was just using a few generic covers. but now i have a different generic cover for each genre and about 20 other real album covers, that change a lot of times.
and the more they change the more sluggish monkey makes the mouse and the faster any of the errors listed in my first post in this thread. appear

so that has got me thinking it could still be that album art memory leak that was thought to be fixed..

but i need you others with the same errors to reply as jiri is beging to think it is only my computer but i know you others have posted some of the same errors in other threads.

so reply and let them know how many have the same things that need fixed.

edited in. just an idea but the thought just hit me that i did at one time set up the trial of zonealarm pro and told it to auto configure my 9x computers.

and those are the computers i am having most the troubles with. but i have long since updated zone alarm and went back to the free firewall.

so i am thinking could zonealarm have messed up the computers some how and left them messed up when i took out the free trial?

if so what did it leave that would make the memory leak or could it have left something that made the memory leak in monkey.?

any one else have any idea if they also used the free trial of zone alarm pro on their computers and that might have caused their errors?

confused · Post by **confused** » Fri Jan 20, 2006 5:19 pm

no it does not seem to be the old zone alarm trial.

because i did a clean install of zone alarm free and the errors still show up for me.

Guest · Post by **Guest** » Fri Jan 20, 2006 6:10 pm

On Canvas not drawing error, the most common assumption is low resources, but I did read somewhere that it can be caused by a coding problem in Borland. May not apply here, but if I can find it again, I'll let you know.

Guest · Post by **Guest** » Sat Jan 21, 2006 11:02 pm

this is just to let you know the erros are still happening

but someone said in another post some place that they thought it was the skin feature in monkey causing the error.

is it possible that is correct? as the skin does connect to the explorer shell.

and the shell seems to what crashes with the canvas does not allow drawing error.

how about checking the way the skin connects to the shell. it might be a buggy connection?

if it is please see if you can fix it. as i really do like to use the skins.

rovingcowboy · Post by **rovingcowboy** » Fri Jan 27, 2006 12:34 am

okay for anyone else out there trying to figure out what is going on with the same type of errors on your computer. and trying to help with this error message.

i have just tonight tried to find the memory leak in the computer in other programs. here is what i did.

i took two huge half hour long wav files both halfs of a conncert and opened them in a wav editor both at the same time so all was held in ram. about 900 mb's or so in ram i copied the second half so there would be more ram taken up then there would have been if i cut it. and then i pasted it on to the first half of the concert and saved it to make it one file again.

no memory leak symptoms or any sticky mouse stuff or anything it worked like it should.
it only started the symptoms of a memory leak when i opened monkey and tried to add the concert in the database.

the reason i use windows 98 for the jukebox is simple.
windows Xp and Windows me on these other computers Can NOT handle the large files they crash. and they are faster and have more ram? but they crash?

the old work horse win98 don't crash on them large files.

no idea why that is but the computers do that?

rovingcowboy · Post by **rovingcowboy** » Fri Feb 03, 2006 11:12 pm

okay i think i found the cause of the error and it seems to be windows os its self.

but it is not a bug with windows it is how windows and monkey interact.

i sent rusty a huge doctor watson report that was done when the error listed here in the orginal post thread, had all happened at the same time and were on the screen.

what i did was cause all the errors by doing the editing to make it happen when i had dr.watson running when monkey crashed, instead of getting the alert of canvas does..... draw.. it popped up a doctor watson scan panel and took a picture of the system,

in short as far as i can tell with out being a programmer this is what doctor watson's report is saying.

1 media monkey preformed an illegal operation, by trying to access a dll file that was no longer there or was curupted.?

since this happens when i am editing i belive that monkey is using a dll file it loads in to the resouces at start up, and it then stores the information into ram until it reaches a certian amount of data then trys to write it in to the dll file.
but windows does it cleaning out of unused dll files or the ram cleaner does the cleaning out which removes that dll file.

and that causes the memory leak and the crashing. reason i think this is the answer is because monkey locked up on me for no reason the other day it was playing along and just locked up i was not even near the computer so it was not caused by editing.. that is what made me start the dr watson program and try to find what this really is caused by.

so it seems monkey's needing a dll file to be stored in resouces as long as monkey is running, and windows or the ram cleaner comes along and removes the dll files that have not been used in a certian time length.

and thus makes us crazy with these errors.

SUGGESTION TO FIX IT.

make monkey load the dll file in to the swap file and use it there so it does not get kicked out of the resources and crash monkey.

of course i am still waiting for rusty to confirm the trouble is the dll file being kicked out. but that is what the dr watson report says so i hope it is what is causing it. because this error has been getting posted here since 2003.

rovingcowboy · Post by **rovingcowboy** » Thu Feb 09, 2006 4:24 am

rusty have you looked over the dr watson report?

i can not figure out why nobody else seems to be able to recreate this error.

i have recreated it with and with out the skinning engine and with and with out other programs running except those that are hidden from the use as windows needs them and cant be shut down.

but i have had only system tray , explorer , mediamonkey exe, listed in the task manager as the only thing running..

and i get these errors all the time. there is nothing else running on the system to cause it. and nothing happens until i start using monkey to edit the song tags.

i ran the case script the other day and sure enough not even using the keyboard when the script loaded all in to its cache to edit all the resources were used up. because windows posted an alert of " your resources are 99% used close something or your computer will stop responding"

the computer did not stop as i have the temp folder monkey uses on the empty 5 gb hard drive i use for the temp folder and the swap file. it took longer but it did not crash. so having only monkey and windows running helped to correct the trouble.

also i just redid all my songs storage locations. i moved them to new tag orders and monkey did the same thing it used all the resources and continued to move the files but very slowly. i tried it this time with the resources monitor running and the speed at which they were used up was the same speed as monkey goes when loading the data in to its cache to do the editing too.

each time with the case script and the moving of the files the only things running were windows os and monkey and the resource meter which it showed all used resources were returned to empty when monkey started to tag the files.

all this is telling me that it is not only the missing dll file that dr watson said was missing but it seems that monkey hogs all the resources when it is editing. this is not any trouble on winxp right now. since winxp uses the ram stick for resources but some one with a million songs or more decides to move the whole archive to a new tag order monkey will eat up all the ram in xp to do it, and crash xp.

i seem to have found the memory leak i mentioned. it appears to have been the program called tclock there was an option for it to monitor the cpu cycles and that was checked.

i unchecked it and there seems to be no symptom of memory leak now only when monkey eats it all up to do the editing.

oh yeah it used all the resources up at just about 400 files being worked with.

confused · Post by **confused** » Mon Feb 13, 2006 4:17 pm

i hope the docotr watson report helps them because the not using skin thing did not help me either i still have the troubles too.

agentsmart · Post by **agentsmart** » Thu Feb 16, 2006 8:19 am

you are not the only one confused i hope this pile of errors gets figured out fast also.

agentsmart · Post by **agentsmart** » Thu Feb 16, 2006 8:27 am

since winxp uses the ram stick for resources but some one with a million songs or more decides to move the whole archive to a new tag order monkey will eat up all the ram in xp to do it, and crash xp.

has anyone with that many songs on winXp tried to move them to a new mask order?

maybe some one should to see if it will lock up xp if it does lock up xp then we know it is an on going error dealing with how windows or monkey handles the resources?

confused · Post by **confused** » Mon Feb 20, 2006 4:26 am

roving cowboy have you found anymore out about it?

what did rusty say if anything?

there are others posting they have the same trouble on win 2K and winXp.
so you are not alone with this as i have it also, and agentsmart, and now newtomediamonkeyuser has it on win 2 K, and thefaceman seems to have it on winXp

rusty and jiri this does not just seem to be cowboys computers as all us others have the same thing.