Wim,

The performance issues that I see on your uncorrupted DB are mainly in the Art & Details view (where MM doesn't display any content until the entire DB is read). That's tracked at http://www.ventismedia.com/mantis/view.php?id=8145 .

-Rusty

Hi Rusty,

Yes, the high CPU usage was remarkable too (also happens in MM3 often, by the way!) but I simply thought that was caused by the fact that my library is big.
But apparently not?
And do I understand well that you could really DETECT the cause of that high consumption - and repaired it?
I don't understand 100% of the text in the thread you mentioned. Sorry to bother...

Wim,

There is some corruption in your MM4 DB that is triggering high CPU utilization / instability. This is tracked at: http://www.ventismedia.com/mantis/view.php?id=8122

-Rusty

Never had any firewall trouble for accepted programs.
As said in other posts: most of the problems gone now I downgraded back to MM3 again...

WimYogya,

I've never seen such an error either. It seems that something in your environment is causing a variety of strange behaviors.

Could it be some sort of firewall interaction?

-Rusty

Well I've never seen this happen myself or reported and you indicated trouble downloading podcasts. My advice still stands though.

Nope, the internet connection is good - we do have powercuts (average 1x per 2 days for 2 hours) but apart from that the internet itself is stable and fair in speed.
Sometimes even vieuwing streaming video is possible.
So don't blame the Indonesian infrastructure - this time.
I think the cause is completely different, so I ask the developers to have a look.
It happens TOO frequently!

That might be caused by the poor internet connection you have. In those cases you might want to save the log from DBGView and send it to support yourself: http://www.mediamonkey.com/support/inde ... &_a=submit

Too often MM encounters a problem and says it creates an Error Report that I can send.
Then I do my best to inform MM what I was doing, click on SEND, but in more than 50% of the cases that is useless.
The sending progress bar pops up, says there is connection with the server, the bar completes... then a popup window: HTTP error code 12019 and a second one: Sending message failed.
Why?


UPDATE:
In this case the error didn't seem to be fatal: the bugviewer continues and shows ongoing activity (scanning new tracks).
The header of the undsendable Error Report was:
ACCESS VIOLATION at address 0084AF10 in module MediaMonkey.exe read of address 0000000C
No clue what that means.

Clicking that Error Report message away was useless: it kept repeating itself and created an unstoppable cascade of popup messages that I cannot repeat here now, simply because the waterfall froze MM completely now. So I must terminate it with the TaskManager, will then save the dbgviewer log (still running) and figure out what I must do with it - no experience yet...