Intermittent error on closing WPF window causes failure to find window in open/close scenario in a loop

Progress® Telerik® Test Studio® Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 03 Apr 2023 21:17 by ADMIN

ADMIN

Ivaylo

Created on: 02 Jul 2015 10:23

Type: Bug Report

Intermittent error on closing WPF window causes failure to find window in open/close scenario in a loop

With the tracelog ON the application can find windows and will run ok (except for the memory leak).If you turn the tracelog off, it will fail after a couple of iterations.(This is the registry key in HKEY_CURRENT_USER\Software\Wow6432Node\Telerik\Test Studio\TraceLogEnabled )

Application and test code to replicate the problem is shared internally.

5 comments

Matthias

Posted on: 11 Sep 2017 15:05

Hi Tomasz, Hi Elena,

As described in this bug report [1], we suffer from this issue already a couple of years since we are running more than 400 UI Tests every night and 2 - 3 will fail during each run. 

Our execution environment is Windows Server 2016. 

@Tomasz: Could you already produce the issue on Windows 10 machines? 

@Elena: What is the status of this bug [1]? Will this be fixed?

Thanks,
Matthias

[1] - https://feedback.telerik.com/Project/161/Feedback/Details/162947-intermittent-error-on-closing-wpf-window-causes-failure-to-find-window-in-open-cl

Tomasz

Posted on: 05 Sep 2017 09:46

Hi Matthias,

I have the same problem in my tests and I cooperate with Support in tracking it. Please read the topic on forum: 

http://www.telerik.com/forums/sometimes-dialog-windows-are-not-identified-by-testing-framework

and if You have some new observations please write in this forum topic.

Matthias

Posted on: 28 Aug 2017 14:56

Dear Support,

Is this bug being addressed? We are also facing that issue quite often. We have more than 400 tests and during each nightly test run we have about 2-3 tests that fail due to this issue. Thus, that issue is severe and creates a lot of hiccups.

Best regards,
Matthias

Tomasz

Posted on: 14 Nov 2016 11:49

Is this problem has been resolved? I'm using 2015.3.1314.0 Test Studio version and have the same problem.

[11/09 16:31:03,WpfApplication1.exe(5736:1),Error] BrowserRemoteClient.Disconnect() : Could not join the listener thread even after two 1-second wait attempts and an interrupt.

Is there any way to avoid this problem?

ADMIN

Konstantin Petkov

Posted on: 03 Sep 2015 14:24

The problem has nothing with the logging, it's just quite specific to the communication. We actually fail occasionally on disconnecting while closing the window, the error can be seen in the trace log - this is a problem on disconnect:

[09/03 17:03:31,WpfApplication1.exe(7156:1),Error] BrowserRemoteClient.Disconnect() : Could not join the listener thread even after two 1-second wait attempts and an interrupt.