MySQL Bugs: #53312: Catalog diff report crashes.

Bug #53312	Catalog diff report crashes.
Submitted:	30 Apr 2010 11:48	Modified:	4 May 2010 21:49
Reporter:	Espen Carlsen	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.20 beta	OS:	Windows (XP SP3)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
Frame heading: MySQL Workbench Unexpected Error
Heading: MySQL Workbench has encountered a problem
Errormessage in Norwegian: Den eksterne komponenten forårsaket et unntak.

We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below.

Please make sure you include a detailed description of your actions that lead to this problem.

Thanks a alot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team

Roughly translated to English, the errormessage will be something like:
The external component have caused an exception.

How to repeat:
When I have my database diagram up with a diagram I've made from scratch, I choose the Database menu and then "Generate catalog diff report".
This starts the wizzard.

On the first screen, I leave it at default settings.
(Left catalog->Live Database, Right catalog->Model schema)
Next screen, setup information for my local MySQL server (running on localhost)
Next screen shows status about the connection and that the schemas are read from the server.
Next screen, I choose one of the schemas.
Next screen show status for "Fetch object info" everything seems oki so far.
Clicking the next button will display the "differences found screen" with no data and the error right away.

Tested multiple times and it crashes the same way each time.

What exact version of server, x.y.z, are you working with?

My server is MySQL 5.0.90, version tag '5.0.90-community-nt-log'.
Running on Windows XP SP3.

Also tested with MySQL 5.1.44 and 5.5.1 as database, both also on WindowsXP.

fixed recently

can reproduce with 5.2.20 release version but not with current repository build. fixed in repository

actually this is a duplicate of recently fixed bug #49561