Calibre 0.6.51 Preferences crash

[GexMax]

Hey folks,

First of all thanks for such a great ebook app - i've used calibre for quite some time now and usually everyhting works just like a charm.

But today i updated to 0.6.51 (from 0.6.42) and now when trying to get into the preferences (either by clicking the "big" button or the small arrow and then preferences) calibre freezes up.

The bug seems repeatable and i've tried restarting, reinstalling, deinstalling and "fresh" installing the application - nothing helped.

I'm running Windows 7 enterprise x64 with java 1.6.0_20-b02 (32bit mode).

entry in the eventvwr is as follows:

Log Name: Application
Source: Application Hang
Date: 02.05.2010 14:55:19
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: xxxx
Description:
The program calibre.exe version 0.6.51.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: e20
Start Time: 01cae9f69f272fd0
Termination Time: 15
Application Path: C:\Program Files (x86)\Calibre2\calibre.exe
Report Id: f114880a-55e9-11df-a830-001bfc44cc52

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-05-02T12:55:19.000000000Z" />
<EventRecordID>11259</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxx</Computer>
<Security />
</System>
<EventData>
<Data>calibre.exe</Data>
<Data>0.6.51.0</Data>
<Data>e20</Data>
<Data>01cae9f69f272fd0</Data>
<Data>15</Data>
<Data>C:\Program Files (x86)\Calibre2\calibre.exe</Data>
<Data>f114880a-55e9-11df-a830-001bfc44cc52</Data>
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>

i dont know if calibre itself generates any log files i might add here

thanks for the help in advance

[EDIT]
Disregard this thread, please... maybe i should have tried to reboot the system instead of just the application in the first place

(solution == system reboot - everything seems to be working now...)

-
Jens aka GexMax