MySQL Bugs: #46694: Crash when using "Copy SQL to clipboard" feature

Bug #46694	Crash when using "Copy SQL to clipboard" feature
Submitted:	13 Aug 2009 12:54	Modified:	13 Aug 2009 14:08
Reporter:	cgo2 cgo2	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.16	OS:	Windows (XP SP2)
Assigned to:		CPU Architecture:	Any

Description:
Hi,

MySQLWorkbench crash every time I use the "Copy SQL to clipboard" feature (right click on a table). However, it only occurs on a very specific file we use at work. 

- This file is old (started with previous versions of MySQL WB), contains about 50 tables in 2 physical shemata.
- When I click on "Copy SQL to clipboard" on ANY table, I get a message from Windows that MysqlWB has crashed. Clipboard is empty.
- "Copy insert to clipboard" works fine.
- "Copy SQL to clipboard" works fine on new clean files

Unfortunatly, I don't think I can send the file. So how can I help you with this issue ? 

The Windows bug report :

AppName: mysqlworkbench.exe      AppVer: 5.1.16.4210     AppStamp:4a4a2d79
ModName: grt.dll      ModVer: 0.0.0.0      ModStamp:4a4a290e
fDebug: 0       Offset: 00011c0d

How to repeat:
Right-click on a table then click on "Copy SQL to clipboard" on any table.

as you already noted, it's likely that your document got corrupted somehow. we are improving our document loader to detect such corruptions which were caused by previous versions of WB - but it would be necessary to have a look at your doc to identify the source of the problem in your secific doc.
could you maybe try to make a stripped down copy (containint only one table) of your document which also shows this behaviour and send the file. (you can mark it as private so only developers can see/access it)

good news, thats already fixed in our repository and will be included in 5.1.17 (which will be available this week).

i marked it as duplicate because its the same problem reported in #46025 (even though the report-synopsis is a bit misleading on #46025). i asked for the file just to be sure not to have missed anything when fixing.

thx for the report!

Ok that's a good news ! Sorry for the duplicate then, and thanks for your time. Regards.