MySQL Bugs: #65718: generated wrong sql code, then crashed..

Bug #65718	generated wrong sql code, then crashed..
Submitted:	24 Jun 2012 1:16	Modified:	24 Jun 2012 13:46
Reporter:	Hans Henrik Bergan	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.40	OS:	Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
i saw the program generated the code
CREATE  TABLE IF NOT EXISTS `filefiction`.`files_chunks_associations` (
  `id` BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT 'chunkID' ,
and.. the COMMENT does not belong there, it belongs to `file_chunks`.`id` (if i remember correctly),
So i tried to find out why MySQL workbech had misplaced the COMMENT , and in the workbench, the comment was not at `file_cunks_associations`.`id` (so it was really strange that Export->Forward engineer CREATE --- had placed it there) , then i tried to check for the COMMENTS on the other columns on `file_chunks_associations` , and thats when it crashed.. 

btw unrelated: the PNG images generated from "export" is too much compressed/to low quality in my opinion, would be great if this was tuned to higher image quality!

How to repeat:
i dont know exactly how to repeat the crash, 
i was trying to find a COMMENT in 
http://www.speedyshare.com/9bCZh/schema.MySQLWorkBenchModel.mwb
that MySQL Workbench misplaced when exporting..

(also there's no "confidential"/"private" stuff in this report btw)

Based on stack trace this is a duplicate of Bug #65574.