Bug #64504 | Use "Generate Catalog Diff Report" and Workbench crashed. | ||
---|---|---|---|
Submitted: | 1 Mar 2012 6:07 | Modified: | 7 Apr 2012 19:40 |
Reporter: | veronica lin | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.35, 5.2.38 | OS: | Windows (Windows 7 Professional) |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash, diff |
[1 Mar 2012 6:07]
veronica lin
[1 Mar 2012 7:13]
Valeriy Kravchuk
Please, check if the same problem still happens with a newer version, 5.2.38.
[2 Mar 2012 3:13]
veronica lin
Sorry, but the same problem still happens with version 5.2.38.
[2 Mar 2012 18:51]
Alfredo Kojima
When you get the exception dialog, right click on it and select Copy Stack and then paste it here. Thanks. Also, does the crash occur with any model?
[3 Mar 2012 1:47]
veronica lin
Here is the error message when the MySQL Workbench crashed: -------------------------- 問題簽章: 問題事件名稱: APPCRASH 應用程式名稱: MySQLWorkbench.exe 應用程式版本: 5.2.38.8753 應用程式時間戳記: 4f43fc17 錯誤模組名稱: ntdll.dll 錯誤模組版本: 6.1.7601.17725 錯誤模組時間戳記: 4ec49b60 例外狀況代碼: c0000005 例外狀況位移: 00052cc7 作業系統版本: 6.1.7601.2.1.0.256.48 地區設定識別碼: 1028 其他資訊 1: 0a9e 其他資訊 2: 0a9e372d3b4ad19135b953a78882e789 其他資訊 3: 0a9e 其他資訊 4: 0a9e372d3b4ad19135b953a78882e789 -------------------------- I have two database, in the another one, this situation does not occur. In the database with problem, I add some Chinese comments to describe tables and columns like this SQL script: -------------------------- CREATE TABLE IF NOT EXISTS `test_db`.`test_tb` ( `id` integer not null auto_increment primary key comment '流水號' ) ENGINE = InnoDB DEFAULT CHARACTER SET = utf8, COMMENT = '測試用' ; -------------------------- And the database which I wanna compare for is using MyISAM. I guess these differences are related to the crash. But, when I created two simple databases and compared them, Workbench ran smoothly.
[7 Mar 2012 19:40]
Armando Lopez Valencia
Hello Veronica. Can you please attach a dump of the DB and the model file where you are reproducing this problem? Thanks.
[8 Apr 2012 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".