Unplanned
Last Updated: 09 Jun 2026 09:55 by ADMIN
John
Created on: 29 Apr 2026 08:13
Type: Bug Report
0
Chrome connection failure when clicking specific link during Test Studio execution
When executing automated web tests via Test Studio, Chrome fails to maintain the connection to the application under test. Specifically, clicking a certain link on the customer's website triggers a browser crash, resulting in the "Aw, Snap!" error page.

6 comments
ADMIN
Ivaylo
Posted on: 09 Jun 2026 09:55

Hello John,

Thank you for your follow-up.

As mentioned in my previous reply, please note that disabling web security through the suggested workaround applies only when Chrome is launched by Test Studio for automated execution. It does not affect your normal manual Chrome sessions.

This type of behavior is commonly seen when additional security layers such as Cloudflare are involved. It is not specific to Test Studio alone, and similar issues can occur with other automation tools as well when stricter security policies or anti-bot protections are in place. In such cases, organizations often use dedicated test machines or environments with adjusted security settings for automation.

Our findings are the following:

Error observed:

 

[ERROR:content\browser\bad_message.cc:29] Terminating renderer for bad IPC message, reason 114

 

This means Chrome terminated the renderer process because it detected an invalid browser communication message. In this case, the behavior is consistent with an origin mismatch during navigation.

Most likely cause:

  • The page appears to involve Cloudflare and cross-origin browser activity
  • The automated browser session uses a separate Test Studio Chrome profile
  • That profile may not have the same cookies or trusted state as your regular manual Chrome session
  • Under automation, the page may follow a different challenge or redirect path, which can lead to the browser crash


Why it works manually:

  • Your regular Chrome session may already have the necessary session state or cookies
  • Manual browsing does not go through the same automation-driven browser flow

If you would like to investigate further on your end, you can enable Chrome logging with the following browser arguments:

--enable-logging --v=1

The log is typically generated here:

C:\Users\YOURUSERNAME\AppData\Local\ArtOfTest\TSChromeUserData\chrome_debug.log
Unfortunately, because this behavior is caused by the additional security layer applied to the application, it is not considered a bug in Test Studio. For such cases, we are not able to provide a product-side fix and can only suggest a workaround, such as the one we are currently sharring.

As there is no change required on the Test Studio side, we will proceed with closing this bug. 

If you would like, we can certainly continue the discussion in the ticket you have submitted internally regarding this problem and assist you further there.

Thank you for your understanding and cooperation.

Regards,
Ivaylo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

John
Posted on: 08 Jun 2026 15:45

Hello Ivaylo,

 

Thank you for the update. I saw the steps for the workaround. We are little concerned with disabling the security in the Registry.

Would that be possible to get more details of your finding on the error in your logs? It would be very helpful for us to investigate and understand the issue of the application on our site.

 

Thank you.

John

ADMIN
Ivaylo
Posted on: 08 Jun 2026 13:40

Hello John,

Please refer to the original ticket that was opened for this problem. I've just updated it.

Thank you for your patience and understanding.

Regards,
Ivaylo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

John
Posted on: 08 Jun 2026 13:28

Hello Ivaylo,

 

Thank you for the update. That's a good news!

Please share the workaround with me asap as we need it for the regression we are working on.

 

Regards,

John

ADMIN
Ivaylo
Posted on: 08 Jun 2026 13:21

Hello John,

While we won't be able to implement a permanent fix for this issue, we have found a great workaround. I will share the details directly in the private ticket to keep your information secure.

Thank you so much for your patience throughout this process.


Regards,
Ivaylo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

John
Posted on: 02 Jun 2026 17:33

Hello,

 

May I have an update on the status of the fix for this issue?

 

Thanks,

John