INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed  (Read 2338 times)

globetrotters1

  • Citizen of the Universe
  • *****
  • Posts: 566
Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« on: April 17, 2007, 05:03:30 pm »

With the latest version 207 tested, same...

After a rip of a CD the program displays the "Downloading Images..." box to get the cover art from the Internet.

Over this box the program displays a "please wait..." box to update the YADB database with the album data...

Over this box the program displays a "please wait..." box with the text "Working"

the only way to get rid of all that is to kill the program...

oh and clicking "cancel" button doesn't help anything! :(

Sorry, guys
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72439
  • Where did I put my teeth?
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #1 on: April 17, 2007, 05:17:11 pm »

Sound like something may be blocking the connection.  Vista?
Logged

globetrotters1

  • Citizen of the Universe
  • *****
  • Posts: 566
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #2 on: April 17, 2007, 07:29:36 pm »

Jim,

no, XP SP2 latest version and so on... no Vista (and also NEVER Vista!)

have to comment:

Satellite connection, but no problem there (most of the time at least, although weather dependent)

When I switch off YADB album data update then I get rid of this hang; I assume you run into some troubles if you have to get the cover art AND if you do the album data update together somehow... often it works fine, sometimes it hangs and has to be killed (I'm a nice man and not a killer, so I prefer to stay like that :) - and it's only bad for your YADB database, like this - switching off the update - you won't get my data, too bad)
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72439
  • Where did I put my teeth?
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #3 on: April 17, 2007, 07:48:09 pm »

Firewall?
Logged

Fred1

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 491
  • Change this by choosing profile
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #4 on: April 18, 2007, 03:15:56 am »

I can confirm that on XP Service Pack2.

After ripping is complete, there is a messagebox for a moment that says that MC is unbable to add to database (YADB, i think).

Then it shows a messagebox "Working... Cancel" for an eternity until you kill MC.
You can't cancel with this button, however.

This seems to occur when MC cannot connect to YADB.

Has been working before with no troubles.
No other firewall etc., same configuration as before.

Oh my god, i hope this item will be debugged very soon, because i still have 500+ CDs to rip!
Logged

globetrotters1

  • Citizen of the Universe
  • *****
  • Posts: 566
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #5 on: April 18, 2007, 06:56:52 pm »

Fred,

just switch off "enable Update of YADB database after ripping" in the preferences and you got rid of that... I go sick of killing the program too

Martin
Logged

Fred1

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 491
  • Change this by choosing profile
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #6 on: April 18, 2007, 09:38:07 pm »

Martin,

thanks, that works.
But it means that YADB will get less useful over time, if no new records are entered to the database :(.

Worked very well before.
Logged

John Gateley

  • Citizen of the Universe
  • *****
  • Posts: 4957
  • Nice haircut
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #7 on: April 19, 2007, 01:44:59 pm »

I see some strange behavior here. It's in something that I was going to fix anyways, so I'll get it done soon, but it's a fairly large change so it might not be today.

Thanks,

j

John Gateley

  • Citizen of the Universe
  • *****
  • Posts: 4957
  • Nice haircut
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #8 on: April 19, 2007, 04:13:45 pm »

I believe this is fixed in build 217 or higher.

Thanks,

j

globetrotters1

  • Citizen of the Universe
  • *****
  • Posts: 566
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #9 on: April 20, 2007, 01:18:16 pm »

John,

thanks for this info, you're cool guys! And I mean it... :)

I know out of own experience how complicated such a program can get with time

Martin

PS: I even have time soon to work a bit on your Wiki...
Logged

globetrotters1

  • Citizen of the Universe
  • *****
  • Posts: 566
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #10 on: April 20, 2007, 01:27:05 pm »

John, by the way:

Today I had a very strange phenomenon... I imported a lot of MP3s... playing at the same time another track... suddenly the system got slower and slower and slower and finally got unresponsive

I killed the program, which fixed the problem, restart was no problem

Just a hint that there might be some problem with system resources...

Happened just once until now

Have around 35'000 tracks online now, still a lot missing...

Well, that's all for now
Martin
Logged

John Gateley

  • Citizen of the Universe
  • *****
  • Posts: 4957
  • Nice haircut
Re: Bug MC12: System Gets Unresponsive - MC12 Has To Be Killed
« Reply #11 on: April 20, 2007, 01:34:55 pm »

Hi Martin, Thanks! And the wiki is waiting (Mr. ChriZ was commenting today that it needed some attention).
I actually fixed the wrong thing yesterday: there's 4 YADB accesses that had to be fixed: CD Lookup, CD Submit, DVD Lookup and
DVD Submit. I fixed CD Lookup, but CD Submit is the one causing the problem. I'm fixing the other three today, so it's not a big deal...

About the slowdown - I've seen an unresponsive program during import because of Direct Show filters. If it happens again,
try to narrow down the import to see if one file is causing it. If it happens again, start a new thread with a descriptive subject.

Thanks

j
Pages: [1]   Go Up