Forum Discussion

Hamza_amami's avatar
Hamza_amami
Occasional Contributor
4 years ago
Solved

Can't. open ready API with new mac OS big sur

Hello, I updated mac os, and I can't open Ready API 3.4, its show the splach screen then it crashes Cordialy
  • richie's avatar
    richie
    4 years ago
    Hey Hamza_amami,

    Ok. This is definitely a problem.

    Looking st the logging youve got some issue that relates to the jre, but the logging says the issue is with native code (external to the jvm).

    Id try reinstalling the same version of readyapi,but im not hopeful.
    Next id try upgrading my readyapi to the latest version
    Id also raise a support call with SmartBear, theyll either know about this already and say "dont use those software versions together" or they wont know about it but will need to.

    Before upgrading especially something like an OS its always handy to check the installed software is supported by the OS.

    Ta,

    Rich
richie's avatar
richie
Community Hero
4 years ago
Hey Hamza_amami,

Im running windows so cant reproduce, but have you confirmed v3.4 runs on this new macOS version?

Can you upgrade to a later ReadyAPI! version?

Can you find where the logs are written to on your mac hard disk and see what they say?

Ta

Rich
  • Hamza_amami's avatar
    Hamza_amami
    Occasional Contributor
    4 years ago

    i don't know how to update without opening the application.

    Here are the logs

    • richie's avatar
      richie
      Community Hero
      4 years ago
      Hey Hamza_amami,

      You didnt attach logs, but anyway. You can just download the later version and update the relevant directory. Im assuming it would recognise the previouw mac version (although thats a guess on my part....i just know how ive done it before on windows)

      Ta

      Rich
      • Hamza_amami's avatar
        Hamza_amami
        Occasional Contributor
        4 years ago

        While trying to run through terminal : 

         

         A fatal error has been detected by the Java Runtime Environment:

        #

        #  SIGSEGV (0xb) at pc=0x00007fff203ae0a9, pid=33417, tid=775

        #

        # JRE version: OpenJDK Runtime Environment (12.0.1+12) (build 12.0.1+12)

        # Java VM: OpenJDK 64-Bit Server VM (12.0.1+12, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)

        # Problematic frame:

        # C  [libsystem_platform.dylib+0x10a9]  _platform_memmove$VARIANT$Haswell+0x29

        #

        # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

        #

        # An error report file with more information is saved as:

        # /Applications/ReadyAPI-3.4.0.app/Contents/java/app/bin/hs_err_pid33417.log

        15:45:06,117 WARN  [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [/Applications/soapUI-Pro-4.5.2.app/Contents/java/app/bin/scripts]

        15:45:06,119 INFO  [DefaultSoapUICore] Adding listeners from [/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/listeners/demo-listeners.xml]

        15:45:06,147 WARN  [SoapUIJasperReportManager] The report directory is not specified. The default report directory will be used.

        #

        # If you would like to submit a bug report, please visit:

        #   http://bugreport.java.com/bugreport/crash.jsp

        # The crash happened outside the Java Virtual Machine in native code.

        # See problematic frame for where to report the bug.

        #