Forum Discussion

Leotheras's avatar
Leotheras
New Contributor
4 years ago

Since version 3.0.0 to 3.8.0 ReadyAPI starts for around 10 minutes and ends with Chromium error.

Hello!

We have a problem in our environment, that ReadyAPI i starting and working very slowly. Start takes around 10 minutes, ends with Chromium error, and after we are getting the same error every couple minutes (s. Chromium_error).

 

Faulting application name: chromium.exe, version: 84.0.4147.135, time stamp: 0x5f3b0616

Faulting module name: ntdll.dll, version: 6.3.9600.19678, time stamp: 0x5e82c88a

Exception code: 0xc0000005

Fault offset: 0x0000000000030837

Faulting process id: 0x11428

Faulting application start time: 0x01d740c7110a2c95

Faulting application path: C:\Users\asverchk\AppData\Local\JxBrowser\7.12\chromium.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 43171e1f-acbb-11eb-80e1-a0369ff28a66

Faulting package full name:

Faulting package-relative application ID:

 

ReadyAPI is running through Citrix, or RDP. Installed on Windows_NT, usind JDK-10.

Our IT colleagues keep saying, that it's software issue.

 

Maybe there is a way to connect another Chromium version (it was a proposal from Team)?

 

Thanks in advance!

 

KR,

Artem

3 Replies

Sort By
  • nmrao's avatar
    nmrao
    Champion Level 3
    4 years ago
    If browser is not necessary, there is an option to turn it off. Please try that.
    • Leotheras's avatar
      Leotheras
      New Contributor
      4 years ago

      Problem is - that when ReadyAPI opens - there is "Browser component is disabled" for example in Projects, or Integrations part. It seems it's turned off.
      And even then - "Chromium has stopped working" every 2 minutes.

      • dbilek's avatar
        dbilek
        Member
        4 years ago

        We had the same issue previously with ReadyAPI 3.6.  After adding -Dsoapui.browser.disabled=true to the vmoptions file (located here:  \Program Files\SmartBear\ReadyAPI-3.6.0\bin\ReadyAPI.vmoptions), the error stopped, and the client loaded faster.

        Now we upgraded to the latest client (v3.8.1), and this error message returns, and setting that parameter does not seem to fix it now....but maybe it will work for you!