We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More

Forum Discussion

Ryan_Moran's avatar
Ryan_Moran
Valued Contributor
11 years ago
Solved

.net application plugin/support crashes during script playback

pseudo code: Sys.Process("Infinity").WinFormsObject("frmCATFRAMS").someobject.click(); //after the control is clicked the application performs a CPU intensive task Sys.Process("Infinity")...
  • Ryan_Moran's avatar
    Ryan_Moran
    11 years ago
    Tanya,

    I was skeptical so I gave this a try.

    Predictably this proposed solution had no impact on the issue I am experiencing.

    If the .Find method times out during CPU intensive application processing extended properties are no longer available. I am still unable to work around this without setting the Auto-wait timeout to a value greater than the applications process time. From your code the "mainForm" in this scenario does exist, but is currently "Unresponsive" while processing....during that "Unresponsive" state I am performing a .Find on the form...

    (mainForm.Find(prop,propVal,depth) )...the Find method appears to be waiting up until the auto-wait timeout and then causes the .Net plugin support to crash or become unavailable.
Marsha_R's avatar
Marsha_R
Icon for Champion Level 3 rankChampion Level 3
11 years ago
We went through a period where that happened to us a lot.  I think it was when we were doing a lot of name mapping at once.  Seemed like TestComplete would just get tired and quit reading the mapping and then we would start seeing the Windows info instead of the mapped names.   We tried to track it down but it was taking too long and we couldn't reproduce it at will, so we just learned to reboot when it started happening because it was going to crash eventually and that was the quick solution.   Haven't seen it in a while, but we've been working with the same name mapping for several months.   



Another note, when TestComplete is running slow for us, we can open the mapping for an object and see the Windows info fill in and then switch to the .Net mapping.  I'm sure that we just don't see that happening when it's running at normal speed, but that may lend some credence to your theory about the plug-in.