unhandled exception during debugging

Bug reports.
mikeerh
Posts: 5
Joined: Mon Aug 17, 2009 10:02 am

unhandled exception during debugging

Post by mikeerh » Mon Aug 17, 2009 10:10 am

I am just evaluating your product for our company and I tried the sample "Data driven test".
I tried to step (F11 step into) through CSVConnector class in Ranorex studio - it was terrible slow ( 1 step needs 10 seconds) and then it crashed:

Ranorex Studio Version : 2.1.3.6676
.NET Version : 2.0.50727.3082
OS Version : Microsoft Windows NT 5.1.2600 Service Pack 3
Current culture : German (Germany) (de-DE)
Current UI language : en-US
Working Set Memory : 80100kb
GC Heap Memory : 26952kb

Exception thrown:
System.Runtime.InteropServices.COMException (0x80131C19): All outstanding steppers have not been closed, detaching is not allowed at this time. (Exception from HRESULT: 0x80131C19)
at Debugger.Interop.CorDebug.ICorDebugProcess.Detach()
at Debugger.Process.Detach()
at Debugger.NDebugger.Detach()
at ICSharpCode.SharpDevelop.Services.WindowsDebugger.Detach()
at ICSharpCode.SharpDevelop.Project.Commands.DetachFromProcessCommand.Run()
at ICSharpCode.Core.WinForms.MenuCommand.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

---- Recent log messages:
Failed to append recent log messages.
System.InvalidOperationException: Sequence contains no elements
at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source)
at ICSharpCode.SharpDevelop.Sda.LogMessageRecorder.AppendRecentLogMessages(StringBuilder sb, ILog log)
at ICSharpCode.SharpDevelop.Sda.ExceptionBox.getClipboardString()

---- Post-error application state information:
Installed 3rd party AddIns: [RanorexLogViewer, Enabled=True, Action=Enable], [RxObjectRepository, Enabled=True, Action=Enable], [RxRecorder, Enabled=True, Action=Enable], [Workflow Foundation Designer, Enabled=True, Action=Enable], [ElementTree, Enabled=True, Action=Enable]
Workbench.ActiveContent: [TextEditorDisplayBindingWrapper C:\Documents and Settings\merhardt\My Documents\RanorexStudio Projects\WPFCalc2\WPFCalc2\CSVConnector.cs]
ProjectService.OpenSolution: [Solution: FileName=C:\Documents and Settings\merhardt\My Documents\RanorexStudio Projects\WPFCalc2\WPFCalc2.rxsln, HasProjects=True, ReadOnly=False]
ProjectService.CurrentProject: [CSharpProject: WPFCalc2]

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: unhandled exception during debugging

Post by Support Team » Tue Aug 18, 2009 12:23 pm

Hi mikeerh!
We already tried to reproduce that issue for a while but still without success.
It looks like that it corresponds to the problem which was already posted here: http://www.ranorex.com/forum/unhandled- ... -t928.html
If you know any way or have helpful ideas to reproduce please let us know!

Regards,
Christian
Support Team
.
Image

mikeerh
Posts: 5
Joined: Mon Aug 17, 2009 10:02 am

Re: unhandled exception during debugging

Post by mikeerh » Tue Aug 18, 2009 12:54 pm

Perhaps the crash has something to do with the annoying delay when I step through code in single step!
If I step over using Menu (Debug -> Step over) the step is done immediately.
If I use the keyboard pressing "F10" is takes 7 (seven) seconds for each step

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: unhandled exception during debugging

Post by Support Team » Tue Aug 18, 2009 1:00 pm

I don't know if that has any influence. However, you can get rid of the "annoying" delay, it is caused by setting the Keyboard.AbortKey. If you do not set an abort key, there should not be a delay. Hence comment out the following line:
// Keyboard.AbortKey = System.Windows.Forms.Keys.Pause;
Regards,
Alex
Ranorex Support Team
.
Image