Ranorex crash while editing code module

[caleb]

I am frequently having Ranorex crashes while I am editing code modules in the Ranorex IDE. I will just be typing in a method name and the Ranorex IDE will crash. Ranorex appears from the user experience to be working fine until the point where it decides it has crashed and prompts to submit an error report and restart.

This has happened twice today and last week it happened about 6 times. I have submitted an error report each time but since I have not heard back I thought I would raise it here.

Ranorex 5.1.1
Windows 7

System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
---STACKTRACE---
System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource) +0x10
System.Collections.Generic.Dictionary`2+Enumerator.MoveNext() +0x0
Ranorex.Sharpdevelop.RxTestingUtil.AmbiguousClassNameExists(CaseInsensitiveString moduleGuid) +0x4f
Ranorex.Sharpdevelop.RxTestingUtil.GetDisplayedModulePath(CaseInsensitiveString moduleGuid,String relativePath,String testSuiteFileName) +0x97
Ranorex.Sharpdevelop.RxTestingUtil.UpdateTestModuleName(TestSuiteModule module) +0x4f
Ranorex.Sharpdevelop.RxTestingUtil.UpdateTestModuleNames(TestingOwnerBase testingOwner) +0x15
Ranorex.Sharpdevelop.RxTestingUtil.RefreshModuleGroupTable(String groupTableFileName) +0x73
Ranorex.Sharpdevelop.RxTestingUtil.<RefreshTestingViewsOnDomUpdate>b__0(Object param0) +0x7e
System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state) +0xe
System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext,ContextCallback callback,Object state,Boolean preserveSyncCtx) +0x70
System.Threading.ExecutionContext.Run(ExecutionContext executionContext,ContextCallback callback,Object state,Boolean preserveSyncCtx) +0x0
System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() +0x23
System.Threading.ThreadPoolWorkQueue.Dispatch() +0x9c
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() +0x0

[Support Team]

Hello caleb,

Thank you for reporting this issue.
Please update to our latest version 5.1.2. The bug should be fixed within this release.

Please do let us know in case the bug still persists.

Regards,
Robert

[marttix]

I am also having this issue, even after upgrading to Ranorex 5.1.2.
I have Windows 7, service pack 1 which runs in a virtual machine.
I haven't seen the stacktrace, though. Ranorex just prompts to send an error report
(which fails, probably a firefall blocks it) and then it restarts.

- Martti

[Support Team]

Hi marttix,

Thank you for the information.
We will analyze the issue.

Thank you for your patience.

Regards,
Robert

[paulsfelten]

I am having this issue as well. This is very frustrating because this causes Ranorex to close. This is occurring while using Ranorex 5.1.2.

[caleb]

It is a reasonably involved process for our team to upgrade Ranorex versions given that we have to validate that our iPad, Win8 app, windows and web tests all continue to work. And given that paulsfelten and marttix both see the issue on 5.1.2 we don't think it is worth the effort to upgrade at this point.

Have you reproduced the issue on your end and know when a fix is likely?

[MikeV]

System is Windows 7 Enterprise 64-bit. Just upgraded from Ranorex Studio 5.1.1 to 5.1.2, which solved the lag problem when editing a file in a large Solution (about 2000 .vb code modules). Now Studio is crashing easily when editing a file in the same large Solution.

I can open a few .vb files that are Ranorex Usercode Modules, try to cut and paste from one to the other, and that causes the crash. Also, some simple edits in a single file cause the crash. This is making Studio 5.1.2 unusable for me. I need to edit lots of files fast, and that is impossible now.

I have emailed a couple of crashes from the crash dialog, so please look for those.

I am considering uninstalling 5.1.2 and installing 5.1.0, which was the last version that worked well for this large solution.

[Brent Arata]

Version: 5.1.2
OS: Windows 8.1
Device: VMware, Surface pro 2, Helix

AUT seems to be in a dead lock when resuming the thread that are responsible for running the AUT; when running a Ranorex module that consist of many code modules. In our suite, instead of us binding the code modules to our Ranorex module, we are dynamically allocated those modules via object reflection. I have attached the log but the error seems to happen starting at line 9679

2014-08-29 07:44:00,119 [1] DEBUG- Debugger: Callback finished: ExitThread 5376
2014-08-29 07:44:00,119 [1] DEBUG- Debugger.Process: Debugger event: OnResumed()
2014-08-29 07:44:00,120 [1] DEBUG- debuggedProcess_DebuggingResumed:
2014-08-29 07:44:00,120 [1] DEBUG- OnIsProcessRunningChanged:
2014-08-29 07:44:18,708 [1] DEBUG- Debugger.Thread: .....Thread ISponsor: Renewal Called.....
2014-08-29 07:44:38,710 [1] DEBUG- Debugger.Thread: .....Thread ISponsor: Renewal Called.....
2014-08-29 07:44:38,710 [1] DEBUG- Debugger.Thread: .....Thread ISponsor: Renewal Called.....
2014-08-29 07:44:58,711 [1] DEBUG- Debugger.Thread: .....Thread ISponsor: Renewal Called.....
2014-08-29 07:44:58,711 [1] DEBUG- Debugger.Thread: .....Thread ISponsor: Renewal Called.....
2014-08-29 07:45:18,719 [1] DEBUG- Debugger.Thread: .....Thread ISponsor: Renewal Called.....
2014-08-29 07:45:38,721 [1] DEBUG- Debugger.Thread: .....Thread ISponsor: Renewal Called.....

Let me know if you would like any screenshots, other logs, etc to be uploaded here.

[Brent Arata]

Whoops, Can I please get this topic moved to "Bug Reports"? Thanks!

[Support Team]

Hello,

Thank you for reporting this issue. In order to get as much information as possible and due to the importance we would like to ask you to get in touch with us via email. This ensures that this issue will be fixed as soon as possible.

Please contact [email protected].

Thanks,
Robert