more and more "Access violation" errors

[beg]

Hi,

I am using MM gold version 4.0.7.1511.

The last versions of MM version 3 were almost not useable because it was extremly unstable. I was about to switch to another player.

This gladly improved massively with the introduction of version 4 which worked without any mistakes most of the times.

Sadly I notice that it get more and more unstable again. My feeling is that with each new update it gets more unreliable. I noticed this especially during my last update to 7.1511, but also to a lesser degree for the versions before.

I get following kind of error messages in various situations and a lot - meaning several times a day when working with MM a lot:
Access violation at address 006B27BA in module 'MediaMonkey.exe'. Read of address 00000040
Access violation at address 0048C166 in module 'MediaMonkey.exe'. Read of address 00000010
Access violation at address 0053BC53 in module 'MediaMonkey.exe'. Read of address 00000007

When trying to close MM after such messages it is not possible. It either kind of freezes, or is saying that there is a background process running which can not be cancelled. I have to use taskmanager each time to completely shut it down by force. Sometimes the whole installation (portable installation on a external harddisk) get's corrupted and starts in a kind of old configuration without any of my playlists. I can only correct this by restoring a backup of the programm folders of MM and recopying my database.

This error happens for example very often when ripping a CD with dbpoweramp cd ripper and changing a tagging information (of a completely different CD) in MM. This used to work perfectly fine for many hundred CDs being ripped in dbpoweramp and worked on in MM at the same time in former versions..

I am really afraid that it get's as unreliable and unstable again as the last versions of MM 3. I am working professionally with a huge music archive with MM and changing to another system would be very difficult and hard. I do not care about 99% of all the new features being added and worked on. I simply need a reliable and working MM. It is a shame and absolutely catastrophic for my use if the new features being added are reducing the reliability in such a massive way! At the moment I have to task-manager-shut down and restart MM ervery day several times..

Bernhard

[Lowlander]

You should capture this in a debug log (step 4b) and send it to support: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

[rovingcowboy]

Mediamonkey is seeing the cdrom in the drive and trying to read it, but is unable too which is what those memory locations is telling you, each time it tried to see a unit of mem it was being blocked by dbpoweramp. Because Dbpoweramp was using that unit when ripping the cd, the same unit appears to be the door for all items to see the cd content as i'm guessing because monkey is triggered to try and read the cd, it cant be the unit that says a cd is installed.

Do what lowlander said but only after trying to edit the tags for a cd in mediamonkey without ripping one, to see if the error happens then. If it does then its a major error someplace else in mediamonkey, if the error dosent happen when you dont rip at the same time, then it is as i suspected in the area of trying to read the cd dbpower amp is ripping.
And the debug report will give more help to the guys trying to fix the error.

[beg]

As I was writting:

It used to work fine in previous versions of MM. Ripping with dbpoweramp at the same time when working with MM. It was perfect. I ripped with dbpoweramp (using two programm instances and working from two CD drives) having MM adding the newly ripped music into it's archive automatically. Right after ripping I was able to access and work on the newly ripped music. This worked without any problems.

And I also do get those messages in various other situation, but I can not reproduce them. Suddenly this Access violation message pops up and I have no idea what could be special on what I was doing.. The ripping situation was just an example where it happens very often.

cheers,
Bernhard

[rovingcowboy]

okay then so the only thing to do is since mm is not auto popping up the crash report. you need to run the third party debug viewer and make a debug report using that one. just install it start it and let it run in background then start mediamonkey and then do the ripping of a cdrom with dbpoweramp and when you get the alerts to pop up and make sure you get several of them if possible in short time. then close mm and dbpoweramp and then save the debug report zip it up and send it to the email address in the support section at the top of this page.

that is the only way to find what is causing it since you believe it is doing it for some other reason then the ripping. but since it does it more often when ripping use that to your advantage and make the debug report with it. they will find what is really going on and stopping that section of ram from being accessed by monkey. its also possible the ram is going bad in that chip but hard to tell with monkey. new ram has been known to go bad before so its got a past rap sheet.

[beg]

workstation is running fine with about 30 other programms almost 12hours a day, so I do not think it is my RAM.

I will do again the debug reporting thing.. : (

Also performance gets worse again. It used to be rather fast in the beginning of the 4 versions compared to the last 3 version, but it is getting slower and slower again. Quite regulary I experience "moments" of no reaction by MM of up to 2-3 minutes. I just captured that in my first session of debugging twice now.

I do hope that the developer team manages to keep a stable version of MM when being used on a big archive of music.. At the moment it is borderline for me already. 1-2 minutes of waiting every now and then or access violation errors every day is hard to ignore..

Just for information:
Could I change back to one of the first 4 versions? There are no changes in the way they work with the DB, so I could change back, right?

cheers,
Bernhard

[rovingcowboy]

Yes you could change back to one of the stabler earlier versions of mm4 .
Just a shame you are having all that trouble.

[Lowlander]

Run File > Maintain Library with the option to a complete optimization enabled as that fixes performance issues for most.

[beg]

Hi Lowlander,

I think you could know me by now.. ; )

I am a hardcore user of MM for some years now and I run the library optimization almost EVERY DAY when working on my music/archive adding music and changing tagging.. It does not help. (at least in my case)

Bernhard

[monkeywrench]

Yesterday I was having trouble getting the art finder batch script working (most of the day) ; I was getting no results except for adds and union jacks, so I tried all solutions on your support page:

http://www.mediamonkey.com/forum/viewto ... =2&t=10435

After having read and tried everything on all 111 pages in that thread to no avail, I un-installed MM and did a clean install. The art batch script did not work at first but then after 20-30 minutes it miraculously started working, I was finally able to get the script to work on the new installation.

Today I got an error message but I was using 'auto tag from web' from the tools drop down menu. I have a print screen of the Access violation error. (I can send it if needed)
the error reads:

“Access violation at address 00780F7A in module MediaMonkey.exe. Read of address 00000000.”

So I read these threads:
http://www.mediamonkey.com/forum/viewto ... =7&t=69723
http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

and installed the MM debug version, because I can't find the error logs under AppData folder nor anywhere on computer for that matter.

The next error occurred while editing and adding album art by right click on image: right click edit album art did not work so I used right click properties then selected an image from the art tab using the file browser to add image but this did not work either. I have learned that if you change the selected “genre” from the Genre pane and come back to the album I was previously editing then it works again sometimes. No access violation error message appeared but MM froze for 20 sec and a popup appeared: MM has encountered a problem asking me to send a report.

It seems MM is unstable at this point, even after a clean install. An other thing worth mentioning is that my firewall anti-virus may have been scanning my hard drive at the time of editing album art (mentioned above), i'll keep a better eye open on which processes are running next time because I'm sure MM is going to crash again.

I hope this info is usful for others that encounter the same type of errors.


Sytem info:

MM Gold version:4.1.0.1692

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name LAP
System Manufacturer Acer
System Model Aspire 7750G
System Type x64-based PC
Processor Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, 2001 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Acer V1.09, 7/04/2011
SMBIOS Version 2.7
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name lap\nic
Time Zone W. Europe Standard Time
Installed Physical Memory (RAM) 8,00 GB
Total Physical Memory 7,98 GB
Available Physical Memory 4,60 GB
Total Virtual Memory 16,0 GB
Available Virtual Memory 12,4 GB
Page File Space 7,98 GB
Page File C:\pagefile.sys

[Lowlander]

Do step 4b and send to support: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

[Guest]

New error appeared:

Access violation at address 007879CC in module 'MediaMonkey.exe'. Read of address 64007305.

I was editing properties of one album and MM Debug popup appeaed as I tried to save changes. The changes did not take effect.
I filled in the report and pressed send.
Dbgview in the background did not log anything, it was set to log and save.

Will try again.

[Lowlander]

If DBGView shows nothing you may have to run it as Administrator.

[monkeywrench]

I restarted DBGView and it worked, I tried to reproduce the error, but this time all i did was left click on an album to select it and MM froze. However the MM error window poped up so filed the report again and sent it again. I had to force MM to close with task manager becouse it was not responding.

I have now opend a ticket and uploaded my DBGView.log to the help desk.