Horrid u201Ccrash for no apparent reasonu201D in the crystal viewer

Question

Hi
We have embedded the new 2010 for VS crystal viewer in our .NET 4 enterprise application.
We are sometimes seeing this crash:
at CrystalDecisions.Windows.Forms.PageControl.OnMouseMove(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseMove(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.UserControl.WndProc(Message& m)
   at CrystalDecisions.Windows.Forms.PageControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
This seems to happen if the report viewer happens to show where the mouse is and the mouse is moving. This is hard to reproduce but has happen on a number of different machines.
We are running the Crystal viewer on a form in it own message loop with Application.Run(TheForm).
We are running 32bit_13_0_1 crystal runtime.
Any help appreciated.
Regards
Daniel Rowe

Answer 1

Also note. Another user had the same issues and the cause was fixed by updating their video card drivers.
They too were on CR SP1.
For all those who find this post please try it first. In the Adapt and Fix in SP2 We have altered the way we render the report objects and added some changes to the order the objects are rendered but it appears the bottom line cause of this is the video card drivers not being able to keep up and throwing an exception which causes CR to crash.
Don