TestComplete 7.50 hangs when entering code

[kalli]

When entering code in TestComplete 7.50 the application seems to immediately start parsing the code, causing the cursor to flash rapidly for several seconds.

TestComplete becomes quite unresponsive while this is going on, making code editing a tedious chore.



This was not the case in 7.20, so I'm downgrading to that version while this is unresolved.

[kalli]

Sorry, this doesn't seem to have anything to do with v7.50, but rather performance in Windows 7. Has anyone else had problems here? And is there maybe a workaround?

[kalli]

It seems that every time some code is edited, TestComplete starts parsing through the whole project's code. So projects with many units and lines of code become quite heavy, while a relatively new project is light.



I cannot reduce my project's size so this situation is quite terrible for me.

[Dmitry_Nikolaev]

Hi Karl,

>> It seems that every time some code is edited, TestComplete starts parsing through the whole project's code.

Could you please record the problem using a screen recorder, so we can see the problem as it is?

You can use the CamStudio free screen recorder for the recording. You can download it here:

http://camstudio.org/

Run the recorder, set the "Options | Video Options | Quality" to 50 and record the issue.

Send me the video via our Contact Support form:

http://www.automatedqa.com/support/message/ 

If the file is too large, please let me know via email and I'll give you access to our FTP server, so you can upload it there.

Thanks in advance.

Also, we have an appropriate suggestion (to improve performance of the Code Editor panel) in our DB, and your message has increased its rating. Thanks.

In the meantime, you can uncheck the "Auto Pop-Up" option in the "Tools | Options... | Panels | Code Editor | Editing" dialog (see the "Editing Options" help topic) to disable the automatic pop-up of the Code Completion window. This should improve performance of the Code Editor panel.

[Jyoungfl]

Include my vote on the code editing performance.  I am also experiencing these slow downs, which I have found are far more pronounced with working with an editor that is in network mode and the project is located on a remote file share. 



After moving my project local, the performance increases, but still takes some time opening up additional workspace windows.



As a suggestion can someone post performance tips related to working with projects on a network environment for distributed testing.  I have already followed the recommended performance tips in the FAQ, but this issue still remains.



Thanks,

[YMinaev]

Hi Jason,



To help us investigate the issue, please zip your entire project suite (the project suite that causes slowdowns when working with it via the network) directory and send us the archive via our Contact Support form.

[kalli]

I'm afraid I'm not at liberty to send my project outside my company due to confidentiality issues, but I'll give you the code metrics:

Number of lines: 15057

Number of routines: 935

Number of units: 34



All of my unit files are on the local disk, not on a network drive.



This does not seem to be a problem for a newly created project with only one unit. I've tried that out and the performance is fine, which leads me to conclude that the project's size matters here.



Also, this is more of a problem when working through a remote desktop connection where the host machine is running Windows 7. Not a problem when working directly on the host machine or when remote desktopping to a machine running any OS other than Win7. That leads me to conclude that this is also a Windows 7 compatibility issue.

[YMinaev]

Hi Karl,



As far as I understand, you experience the problem only working via the remote desktop connected to the machine with Windows 7. When you work on the machine with W7 locally (not via the remote desktop) - the performance is fine. Am I right?



Try updating TC to version 7.51. Does this change anything?

[kalli]

Hi Jared.



Yes, this is exactly as you describe.

I've upgraded to version 7.51.667.7 and still having this problem, I'm afraid. See attachment.

[dcadotte]

I have been seeing this issue for quite some time in versions prior to 7.5.1 and regardless of OS. It also occurs regardless of whether the project is on network or local. I do think it may be size related.  Metrics for my project are:  77,526 lines, 922 routines and 40 units. The 'parsing scripts...' action can freeze the editor for a few seconds to a couple of minutes. AutomatedQA currently has my project for a memory issue. Feel free to check it out on this issue as well.