En-Mass Errors

[rovingcowboy]

no i have not found anything else out about it.

only that it seems to be happening with new or clean installs.

as i have always over installed each new version then i did a clean install of version 2.4 because of some other error i had and that is when the editing errors started to happened.

it happens when i do one song at a time and keep doing them until i get to a total of songs edited in one edting sesion of around 30 to 40. and if i do the case checking with the script it does about 400 before it locks up.

both ways are mass editing.

i did not get anything back from rusty or jiri only that they can't reproduce it and will keep trying to find out what it is.

but it is getting to be troublsome since you the others have now found it also on your computers.

[Guest]

i think i have gotten close to the answer i am still checking on this last idea but it seems to be the way monkey and windows handle the prioitys of the windows shell.

not sure but about that but this is what i have done.

1. i was running the windows cpu in "REAL TIME" making it fast
2. i had all the errors listed in this thread.
3. I just set the cpu back to default prioity and am testing it.
but so far i have not got the persistant child window when i minumize
to the now playing window.
that is a good sign but it did that to me before.

if it is the fact that monkey and windows shell can not handle the real time mode for the cpu then that might be why i was getting the error and not most of you. but as i said i am still checking it will know more later today.

roving cowboy / keith hall.

not logged in just stopped by to say this message.

[rovingcowboy]

i am still checking on this real time idea.

but it seems that might very well have been the trouble with the errors.

but although the now playing persistant child window no longer showed up today the level anaylizing of the songs still stops at around 30 songs depending on the size of the file is what i think stops that from doing more.
which means it can only load so much in to the cache?

but why it requires some time off as in days or weeks to do any more leveling is unknown unless it is because i was setting the backgrouind prioity for it to the highest and that makes it mess up too.?

i just don't have enough new files in the computer yet to do a good job of testing the not drawing error, and this real time idea?

but it seems that the missing file that doctor watson said must be something to do with the access program because i don't have microsoft access on that computer.

doctor watson report did say that if the task bar was acting strange then i should close media monkey exe. now that i took the real time mode back to the default priority mode. that seems to be what the dr. was talking about.

so i am hopeful that the not drawing error is also fixed but not sure yet.

[Teknojnky]

I don't know why your so in love with real time mode, that can bad for windows because it does not allow any other background processes to run properly. Besides that window 98 is like ancient.

[Guest]

it may be old but it still runs on that other computer.

i still have some isa slots on that mother board. and some stuff to plug in to them.

but i am just using that computer for a jukebox i was using a higher prioity for the last couple years. i just changed to real time seveal months back? come to think about it that is just about the time the errors showed up?

but they do seem to be gone now that i put it back at default prioity but boy is that old pent 2, 266 slow on that setting. still i been messing with it all night.

seems to be the songs are playing as normal but still have not put new files in the computer yet to test the canvas not drawing but i think it is fixed. because of the prioity thing. still i will check it some time.

if you have several thousand usa dollars that you can GIVE me i will buy a new system to use for the jukebox but i am broke and the old system handles 30 minute long wav files where this new one won't.

roving cowboy / keith hall not logged in just passin' by the fence today.

[confused]

how long does it take to download some songs and readjust them?

i also use realtime and am waiting to see if you are right before i take it out of real time.

[Guest]

yes it was a long time confused but they kept updating the versions on me so i had to put in more and more songs.

but i have found this error still shows up in monkey with win98.

it seems to be the auto fill code that can not keep up with the backspacing and changing the letters when you type.

that causes it mostly which also could be the auto fill using too much memory? and causing the canvas does not allow drawing error.

that is the only suspect in this error that i can find left? to be the cause of it.

what do you think rusty and jiri?



roving cowboy / keith hall.

just reaching over the fence to post this message.

[nocreek]

Cowboy

I just picked up a Gold version (2,5,1,934) several weeks ago. I am having the same problems. Almost to the letter.

System is:
W2k Pro sp4 w rollup1
Abit NF7s2
AMD 2600+
1g DDR 3200
ATI 8500 DV

I have had a continuning series of very similar problems.

-Unable to Volume level more than 25-30 titles at a time (screen redraw failure)
-Crashes on MS Bugcheck with WinDbg crash analyze shows to be in numerous kernels - some showing a double fault in the processor and also stating machine fault
-Lock up in screen redraw - needing to stop application via Task Mngr
- Varying time and file(title) editing of ID3 tags before either crash on Bugchk or screen redraw failure (varies from 20 - 300 files???)
- Quite occasionally exiting MM and starting another program (any one) a MS bugchk crash occurs or screen redraw failure. These occur shortly upon starting of the program.

No problems occur of any of these nature if during any boot/reboot of system does not involve opening MM. Therefore it is reasonable to assume(remember the assume thingy) that MM is the offending program.

What I have done to try to address:

Installed MDAC 2.8 sp1
Installed MS-Jet (newest from MS??)
Reinstalled - after uninstall of ALL system drivers for MB & ATI card
Installed MM debug and trapped screen rewrite crash during volume leveling
Jiggered with MM ODBC options (increased page timeouts to 10s and buffer to 3072) without any success.
And Lord knows how many other small incremental steps.

Love the program, just wished that the future feature issue would become a secondary issue until this version becomes rock solid. Overall this program rates a 8 in my book(1-10). Just need to find out what this maddening instabilty issue is. I know that not everyone has this issue, but for those of us that really see the beauty of this Monkey - we would like to have a bug free issue also.

Also I upgraded to the Gold several weeks ago but have been using the freebie for about 3 mos. During this time I have dompletely reinstalled OS JUST prior to installing the Gold package. I had hoped that the Gold package may have proved a bit more stable. No such luck!!

[jiri]

Did you e-mail the debug log you captured?

Jiri

[nocreek]

Jiri

I sent a brand new capture to bug report after I made first post. I am able to reproduce error without fail anytime I am doing volume leveling. I stated in bug report that I have not found any system failures, i.e. MS Bugcheck crashes or screen rewrite errors/lockups if during any boot/reboot I do not use MM. Anytime I use MM I may experience the above problems either within MM or very soon after exiting or if switching across programs while having MM in background. So as I stated earlier I assume (remember assume) that the offending module is launched by MM. As an aside I have not really noticed any significant change in memory usage patterns while in or after leaving MM, unlike the problem Cowboy has had. I am running W2K Pro where Cowboy I guess is using 98SE which may account for the mem leakage problem.????

Jeff

[Guest]

no its even older nocreek i am using win98 but i get the same errors on winMe.

the memory leak seems to be an option setting in the tclock program so i turned it off.

but i sure am glad you posted your getting the same thing i am and on a different os. as you can tell i been going nuts trying to find the cause of this.
but it does not seem to be the real time like i thought since it is doing it in the default priority.

roving cowboy / keith hall.

just a leaning over the fence rail again.

[guest jiri rusty peke]

i posted with your names so you would be more inclined to read it faster.

here is what is going on with monkey,

i know not what is the reason it does this but this is what is going on.

1
monkey hogs memory on start up. and keeps it when not needed for some reason.

2.

when editing monkey is trying to open some program for some reason.
and when it trys to open the program there is no memory and the canvas doe's not allow / can not draw alert's pop up by the hundreds.
i presume it is showing one alert for every thing that needs drawn on the screen and can not be drawn.

what is doing this is monkey. it is no other program that is doing this.


A; Reason i know this and just found this out.

a 1. i have been having no trouble for the last couple weeks when i run the msagent program called djamp.

a 2. i have several scripts running all day and the msagent djamp program.

(msagent = microsoft agents, = cartoon characters you can have interact on the screen with you and the computer by way of doing comic stuff or usefull stuff of starting programs or being a virtural dee jay. and saying the songs and names. msagents have a computer voice.)

there is no trouble when running that program. or the scripts
none that is from monkey anyway. or that will mess with monkey.

the thing that happened is this. i had shut the script i use to run all day as a little msagent screen clown that makes no noise and does not speak, i only use it to keep the msagent server running all the time.

i had also shut down media monkey to add in more songs to the computer.
when i started monkey up i had not closed djmap so it was already running no trouble from it as normal i then played songs on the playlist all was going normal and working fine.

then all the canvas does not allow drawing errors showed up again
i was not even touching the keyboard or mouse and it was just running the nomral stuff as it did all morning.
there was nothing going on any different then before i shut it down?

except
i had not started that msagent script to run my little clown i was going to leave it off.

then i seen that the script i use for a screen saver that plays a bouncing ball msagent across the screen was trying to start. at it was time for it to start.

and that is when the errors started.

so knowing that djamp has to start and stop the server that runs the msagents.
and the djamp was not using the msagent dee jay at the time of the crash.

then the server for the msagent was trying to start to run the screen saver and it could not get any memory.

how do i know it was the msagents server trying to start.

simple
i had to restart monkey but this time i started the little clown script that runs all the time and keeps the agent's server running.

and then started monkey and then sat there and waited for the screen saver to run again..
bingo no more alerts.
so it was the fact that the server was trying to start, and monkey did not let it.

it is in the other room i just checked and the screen saver has been run several times now and still there are no more error alerts.

since i started the script to keep the agent's server running first before i started monkey then monkey could only grab so much ram and as long as i leave it running then monkey can't get the ram the agent server uses.


4.
so the trouble is the fact monkey hogs all the memoy and refuses to release some for other programs that need some to start.


now what program / programs, does monkey try and start when you are doing editing of song's properties or when your working with your database information?

which ever that is and how ever many it trys to open one of them will not get memory that it needs and crash monkey.

that is what it is doing but you have to figure out why? i can't? i been lucky in finding out this stuff but i can not do code?

roving cowboy / keith hall.

just reaching over the fence to post on the board.

[Guest]

it is not another program it is in fact monkey running the sound player twice?

here it is

whom ever reported that they heard double playlists starting up.

i have confirmed it. i am getting the same thing. i have been closing monkey with an empty playlist but i did not this last time and i also got the double playlists.

i think this explains the making threads when not playing.
also playing the songs twice. and other errors that seem to be along the same line including the en mass errors i been reporting on for months.

as playing double playlists will eat up all the memory and cause all the above errors. just why it is not playing sound on that first playlist is unknown.
but it is playing the playlist it had when you closed monkey the last time.

i use monkeys playlists but i control them with pekes scripts although i don't think it is pekes code that is doing it as there are too many other's with the memory style errors.

i have sent email to you rusty. trying to explaine it for you a little more.

[confused]

so that makes sense i also got the songs playing twice, i also did try it with out real time and still got the errors. it would have to be something to do with memory, and the multiple playlists would hog memory.

[rovingcowboy]

updated orgianl post with what is fixed and what seems to be the cause of the errors. check it out.