MySQL Bugs: #49488: Print preview gives "Unhandled exeption has occured...."

Bug #49488	Print preview gives "Unhandled exeption has occured...."
Submitted:	6 Dec 2009 14:09	Modified:	23 Apr 2010 5:48
Reporter:	Nick Weavers	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.15 OSS beta	OS:	Windows (W7 Home Premium)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When the print preview option is clicked, an error popup window appears with the message 
"Unhandled exception has occurred in your application.If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Parameter is not valid."    

How to repeat:
Click the print preview option.

this model ships with program

Attachment: model.jpg (image/jpeg, text), 158.73 KiB.

print priview look somewhat (!) different

Attachment: preview.jpg (image/jpeg, text), 62.93 KiB.

got exception when trying to print from preview

Attachment: exception.jpg (image/jpeg, text), 27.00 KiB.

The 3 images I just posted refer to 5.2.10 OSS. After selecting continue in the msgbox listing the exception I was able to continue (execpetion occured when trying to print from print preview).  Looks like a bug in coordinate calculations. Last line of the Danish error message translates to 'The data area that was passed to a system call is too small'

Besides the print preview is useless. Objects do not show where they should. Almost every geometry is obviously miscalculated.

My system is a 17" moderate widescreen (1440*900) laptop with Gforce graphics.

Peter 
(not a MySQL person)

Print preview works for me with 5.2.10 on 64-bit Windows XP.

@Valeriy: did you use same model as I?

I believe that this could affect only wide-screen monitors. Issue could be with specific drivers/graphics system combinations. It is .NET framework that returns the error so it might be related to calling OpenGL routines from .NET/C#.

Was it tested properly with 'wider' monitors than traditional/'old-fashioned' 5:4 and 4:3 (width/height) ratio monitors?

Are you tried the version 5.2.10?. Thanks in advance.

@Miguel .. I got the same error with 5.2.10 OSS whne trying to print from the print preview.  Please look at my screenshots. Obviously geometries are generated outside the valid/legal print area in the print preview.

I believe the problem is related to OpenGL calls on specific screen resolutions and/or with specific hardware and/or drivers with non-trivial models.

I just tried 5.2.10 OSS Beta Revision 4680, but got the same error with a small difference in that I saw an additional popup that said:
"Error while executing plugin (.\wb.printing.wbp.fe.dll::PrintPreviewDialog)
Object reference not set to and instance of an object."

On Ubuntu I get this:

** Message: item_activated: 0x3486d30 -> 'plugin:wb.print.printPreview'

** (mysql-workbench-bin:16564): WARNING **: Could not open editor shared object '/usr/lib/mysql-workbench/plugins/'
** Message: unhandled message 4: wb.print.printPreview finished in 0,00s

How to repeat:

1) start WB from shell
$ mysql-workbench &
2) Reverse engineer database mysql
3) File -> Print Preview
nothing will happen
4) look into stdout ....
you will find the message

I have the same issue as the poster on 10 Dec.  I'm using 5.2.11 beta on Gentoo Linux (compiled from source) on amd64.  Print preview has no apparent effect in the GUI, and you only see those message if you invoke from command line.

Also - selecting "Print..." and then "Print Preview" shows the preview as PDF, and the whole diagram is squished up in the corner of the page.  I assume it's not related to this bug, but I thought the print preview screen would allow me to adjust that.

I think the problem in Linux is already fixed, please try with a newer version.

I dont get any such exceptions in current version. The output shows black rectangles for the tables,
but that is a separate issue.

5.2.15 OSS beta Revision 5053

Print preview window pops up with a message on a grey background saying
"Document cannot be Displayed".
At the same time another window pops up with the title "MySQL Workbench has encountered a problem", and the message "Parameter is not valid". There is a button labelled "Copy Bug Info to Clipboard" and this has provided the following information:

Exception = System.ArgumentException
Message = Parameter is not valid.
FullText = System.ArgumentException: Parameter is not valid.
   at System.Drawing.Imaging.Metafile..ctor(IntPtr referenceHdc, Rectangle frameRect, MetafileFrameUnit frameUnit, EmfType type, String desc)
   at System.Drawing.Imaging.Metafile..ctor(IntPtr referenceHdc, Rectangle frameRect, MetafileFrameUnit frameUnit, EmfType type)
   at System.Drawing.Printing.PreviewPrintController.OnStartPage(PrintDocument document, PrintPageEventArgs e)
   at System.Windows.Forms.PrintControllerWithStatusDialog.OnStartPage(PrintDocument document, PrintPageEventArgs e)
   at System.Drawing.Printing.PrintController.PrintLoop(PrintDocument document)
   at System.Drawing.Printing.PrintController.Print(PrintDocument document)
   at System.Drawing.Printing.PrintDocument.Print()
   at System.Windows.Forms.PrintPreviewControl.ComputePreview()
   at System.Windows.Forms.PrintPreviewControl.CalculatePageInfo()
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

Latest status checked after upgrading to 5.2.16 OSS Beta Revision 5249.

Bug still remains and the generated report is pasted below:-

Exception = System.ArgumentException
Message = Parameter is not valid.
FullText = System.ArgumentException: Parameter is not valid.
   at System.Drawing.Imaging.Metafile..ctor(IntPtr referenceHdc, Rectangle frameRect, MetafileFrameUnit frameUnit, EmfType type, String desc)
   at System.Drawing.Imaging.Metafile..ctor(IntPtr referenceHdc, Rectangle frameRect, MetafileFrameUnit frameUnit, EmfType type)
   at System.Drawing.Printing.PreviewPrintController.OnStartPage(PrintDocument document, PrintPageEventArgs e)
   at System.Windows.Forms.PrintControllerWithStatusDialog.OnStartPage(PrintDocument document, PrintPageEventArgs e)
   at System.Drawing.Printing.PrintController.PrintLoop(PrintDocument document)
   at System.Drawing.Printing.PrintController.Print(PrintDocument document)
   at System.Drawing.Printing.PrintDocument.Print()
   at System.Windows.Forms.PrintPreviewControl.ComputePreview()
   at System.Windows.Forms.PrintPreviewControl.CalculatePageInfo()
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

Bug #51953 has been marked as duplicate of this one

This report is older than Bug #51513, but both have already duplicates refering to them and I started already working on Bug #51513, so I mark this one as duplicate and track progress in the Bug #51513.