Home → Problems →

program freezes and not responsive

• Edit

Katalin Hopkins

Dec 19, 2009 @ 02:24 AM

Hi
my beaTunes keeps crashing and/or becomes unresponsive.
THe program fires up, and it finishes the inspection, however when I click on a solution , such as 'remove disc number from album title' or anything like that, it will start committing the changes and it will become unresponsive as it is in the included file: screen-capture-2.png.
At this point, the only way to quit the program is to use Force Quit after which the database gets locked.
I have tried to uninstall it and go back to an earlier version, but the problem is the same.

I first figured that it is crashing when I try to commit too many changes, but it crashes even when I only try to commit one or at most two changes. This is really frustrating, and annoying also.

Also: When I try to use any of the functions in the Tools menu ( analyze all songs, get music PUIDs, etc) the program will be stuck on the "connecting to server" alert infinitely.

Am I doing something wrong?

if you experienced a crash or other abnormal behavior, you might want to attach log files from /Users/Katalin/Library/Logs/beaTunes

• beaTunes: 2.1.0
• JVM: Java HotSpot(TM) 64-Bit Server VM
• Version: 14.3-b01-101
• Vendor: Apple Inc.
• OS: Mac OS X 10.6.2, x86_64
• Registered as: Katalin Hopkins

• beaTunes.log 4.46 MB
• system-error.log 105 KB
• screen-capture-2.png 17.4 KB

1. Support Staff 1 Posted by hendrik on Dec 19, 2009 @ 07:18 PM

   

   Hi Katalin,

   it seems like something in wrong with beaTunes internal database.

   If there is nothing important in there (i.e. you didn't analyze key or
   BPM ), I would suggest simply deleting the folder /Users/Katalin/
   Library/Application Support/beaTunes/Database/ while beaTunes is not
   running. When beaTunes is next restarted, it should recreate its
   database and hopefully things will work again.

   If you do have important stuff in your database, please try renaming
   the folder /Users/Katalin/Library/Application Support/beaTunes/
   Database/ to some other name (so that you don't just throw away the
   whole database) and restart beaTunes to at least verify whether it is
   the issue.

   Thank you.

   -hendrik

   • Edit

2. hendrik closed this discussion on Feb 22, 2010 @ 02:41 PM.