Ok, please send us (or me directly) some sample tracks that don't work well, we will check them out.

Jiri

[quote="Steegy"]@rovingcowboy: If my words can't convince you, then maybe this simple first result page from Google: http://www.theeldergeek.com/physically_setting_the_page_file_size.htm

Page file size only depends on how large your RAM is, and how you use your computer (mainly as server, or mainly as client). If you have multiple hard drives, you can split this page file over the drives, so each drive has a smaller "disk size loss". Obviously it's best to put the page file on the fastest hard drive you have, and if possible (if you have a fixed 2nd drive) not on the primary one (it's best to offload it as much as possible).
[i]-- I don't want to be nitpicking, I just won't accept wrong information --[/i]


[u]Back to the point of this thread:[/u]
@cmx: If you've found a specific file that causes issues with MediaMonkey (during scanning, tagging, playback, ...) while it normally should work fine, you can send it to the support at mediamonkey (file size as small as possible, or using something like YouSendIt) with enough information.[/quote]


steegy why can't you read the same thing different ways?
you said what i said only differently.? split it up if you want too and put it on the faster hd. same thing i said. only the ram does not really matter, proof is in my systems i use and or take care of. it was one of my systems that 3d game asked for more swap file and i have the large one on there with 500+ mbs of ram so the ram did not matter it wanted more swap file. if i say something its because I've more then likely have done it.
you should know that by now.

as i said before I'm just glad he did not have all that mess to fix and he got it working.

8)

cmx make sure you do a couple logs to double the chance it finds the error.
:D

ok...I'll send the logs(they are HUGE even zipped) but I'm definitely waiting for a specific request for song files themselves.

How is a5 behaving for you?

@cmx do not wait for a dev response to send the logs, the support email is there to accept such things always any time you have a problem and can log/reproduce it.

You can reference this thread in your email, that way if they do have a response on your logs/problems or the problem in general then they can post here if they desire.

@rovingcowboy: If my words can't convince you, then maybe this simple first result page from Google: http://www.theeldergeek.com/physically_setting_the_page_file_size.htm

Page file size only depends on how large your RAM is, and how you use your computer (mainly as server, or mainly as client). If you have multiple hard drives, you can split this page file over the drives, so each drive has a smaller "disk size loss". Obviously it's best to put the page file on the fastest hard drive you have, and if possible (if you have a fixed 2nd drive) not on the primary one (it's best to offload it as much as possible).
[i]-- I don't want to be nitpicking, I just won't accept wrong information --[/i]


[u]Back to the point of this thread:[/u]
@cmx: If you've found a specific file that causes issues with MediaMonkey (during scanning, tagging, playback, ...) while it normally should work fine, you can send it to the support at mediamonkey (file size as small as possible, or using something like YouSendIt) with enough information.

glad you found it but put the swap file back to the size you had it 3 times the ram. just make the min one less then the max that will befine.

am glad it was not the extra stacks being needed as i could not find any way of telling you how to add them in xp? just the tweak program.

steegy if the system has multiple hd's on a raid card the ram does not really matter for the amount of swap file.
it needs to set up to work with dividing the amount for each hd. i don't know the forumla but i just put it one 3rd the size of the drive its on.
and i try to make that the fastest hd to help it's speed. but by putting the requirement size for each hd on the one it gets rather big.
but that allows more room on the other hd's for file storage.

but i'm just glad he did not have all that trouble. 8)

yeah steegy,,,pagefile not the issue....making some final comparisons and tests...but it look like a couple of M4P files are the culprits! Thanks to tekno for getting me hooked up with the debug thing...stay tuned


OK yes....2 days and 6 hours later.....

Isolated to two folders.
Both contain M4P files. (Jimmy Buffet is one of course...lol)

If I deselect these two folders I get a complete scan of my files.

Note:
Several other folders of M4P files WERE scanned in ok. YET, if I try to play one of the scanned M4P files alpha5 generates an error email(sent in).

One other interesting note...

alpha5 returns 121238 total files (artist node)
MM2.5 returns 121969 total files (artist node)

not sure what one is reading the other isn't and vice-versa.....

I have dbqview.log's of the cold crashes on the M4P's if the devs want it. I can also send example of files if needed. I don't want to send all this stuff unsolicited. Please advise.

Thanks tekno....now I can start picking things apart..I can already see there are still issues with Compilations/Various artists

@cmx: your page file is waaaaaaaaaaaaaaaaay too big (yes RovingCowboy, that's my opinion). It's best to set it back so that Windows takes care of it. That way, if Windows notices it runs out of memory, it will dynamically increase the page file size. The "recommended" setting often said is 1.5 times your physical memory. So it you have 512 MB of RAM, the page file size should be around 768 MB. Too much usage of the page file (the part of the memory that gets written to the hard drive) is actually sometimes worse than before (because the hard drive is much slower than RAM). Therefore some servers tend to use less page file size, sometimes even 0. Anyway, if you're using a big page file (and even if you're not), it's important that your hard drive is enough defragmented, so it runs smooth enough.
The most important thing is too look at Task Manager to see how the CPU and RAM usage are. If they're too high (certainly the memory: the memory usage and VM size), then errors are known to occur (in any programs).

in order to get the relevant debug logs, you must run debug viewer before starting MM, make sure 'capture' is on (use the capture menu > capture events, or the magnifying glass toolbar buton), start the debug MM (either alpha or the debug ver of 2.5x whichever your trying to generate the log for), let mediamonky startup and try to recreate the error/problem.

After the problem is reproduced or mm crashes/freezes, you ca save the log and send it to the devs.

Depending on log size, you may need to zip it up.

roving...same behavior occurs no matter tha pagefile size setting...currently set to 4095mg

tek: yeah there seems to be no memory spike, that was my error in reading the system monitor.

I will download and install the link you posted...BUT what are the "relevant log files"...could MM staff give some specific instruction here....hate to just fly blind and wast time.

Feels like it is specific file/files...but i'll be damned if it still crashes if I skip whole folders....arrrrgh

sorry cmx i was typing that last one when you posted the other message.

what are the effects of more page file space. ? better running programs and system.

but the quantums will only improve one or the other a little more then the page file.

example is in a 3d game you are to have a shiny lake on the screen, but you only have the color blue. with out the shine.
give the page file more space, and you get the shine on the 3d game. some programs will send you an alert if there is not enough swap file or page file, for them to use.

just the page sectors were in heavy use? makes me think of you needing extra stacks added. the only way i know how to adjust the stacks is by use of the xteq program in its tweaking stuff it has an option to adjust the stacks. i set my win98 up to 20 stacks then up to 24 stacks i am not sure where i stopped at but it was under 30 spare stacks.

8)

roving cowboy / keith hall.

I have not noticed any spike in memory usage nor have I had MM 3a5 disappear on me.

The first thing I would suspect related to spiking memory would be problems reading a specific file or files.

Narrowing it down to a specific folder would be ideal, but I do understand that is not very convenient espeically when your not sure which out of possibly thousands it could be.

edit:

btw, the debug viewer does work fine with mm3 alpha including alpha 5.

I am using debugview version 4.64 now available from microsoft (they bought out sysinternals) @ http://www.microsoft.com/technet/sysinternals/Utilities/SysinternalsSuite.mspx

did you set the intail page file amount up like i said?

that amount you posted is what i am running on my win98 system windows xp needs more intail setting whic is just the min amount. that should help what monkey seems to be doing is hogging the banana's again. the devlopers will have to slim him down again. make him run on less memory again like they did last year. 8)

roving....I think it might have been wishful thinking....

Upon maximizing the pagefile to 4096 AND letting the system deal with it....same exact crash behavior by A5...

What are the affects of such a high pagefile size?

This computer is used for work and some of the programs are resource intensive...don't want to set the overall focus to system over programs...

also note that it was "pages/sec" that spiked...the actual pagefile usage % and Usage peak really didn't seem to move or have issues at all throughout....

I will now try doing the files in smaller segments....

Any further clarification, ideas or help greatly appreciated....

tek, I might be confused aboput this, but I tried the debug process described in the old post you mentioned and got errors......when I asked about the debug overlay described in the post, I was told it was actually included in the alpha....

either way...I need clarification and help to proceed.