[Webunitproj-users] Issues with child webclients

[Brian K. <bt...@ne...>]

We are having issues with child webclients... some of our web
application's workflows require many browsers windows to be popped up,
so in our tests we have to keep track of all the child webclients.  One
thing we have noticed is that all the child webclients stay open, even
if the javascript executed on the browser closes it.  Is this a bug?  A
work around we tried to conduct in our tests was to close the child
webclient with WebClient.close(), but instead of closing just the child
webclient, all the open webclients are closed and the test stops.  Is
this a bug too?  Also, with all these child webclients open (sometimes
around 10) the process begins to eat up 100% of the cpu and then it
starts to take about 10 seconds just to enter one value on the screen...
sounds like a threading/memory issue - thoughts?

=20

Please advise... thanks,

=20

Brian