Burp Suite User Forum

Login to post

Upgrade from 2021_8_3 to 2021_8_4 failing

Tim | Last updated: Oct 08, 2021 12:55AM UTC

Hi there, When I try to upgrade from 2021_8_3 to 2021_8_4 via the in-app upgrade button (where it asks you to restart), it fails silently. When I download the installer and try to reinstall from the command line I get a Java core dump (this is on Fedora34 Linux fedora 5.14.9-200.fc34.x86_64 #1 SMP Thu Sep 30 11:55:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) [xxx@fedora Downloads]$ sh burpsuite_pro_linux_v2021_8_4.sh Unpacking JRE ... Starting Installer ... # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f5f570dd0cc, pid=18219, tid=18220 # # JRE version: OpenJDK Runtime Environment (16.0.2+7) (build 16.0.2+7-67) # Java VM: OpenJDK 64-Bit Server VM (16.0.2+7-67, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64) # Problematic frame: # C 0x00007f5f570dd0cc # # Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/tbaker/Downloads/burpsuite_pro_linux_v2021_8_4.sh.18184.dir/core.18219) # # An error report file with more information is saved as: # /home/tbaker/Downloads/burpsuite_pro_linux_v2021_8_4.sh.18184.dir/hs_err_pid18219.log # # If you would like to submit a bug report, please visit: # https://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. # burpsuite_pro_linux_v2021_8_4.sh: line 621: 18219 Aborted (core dumped) $INSTALL4J_JAVA_PREFIX "$app_java_home/bin/java" -Dexe4j.moduleName="$prg_dir/$progname" -Dexe4j.totalDataLength=244247197 -Dinstall4j.cwd="$old_pwd" "--add-opens" "java.desktop/java.awt=ALL-UNNAMED" $INSTALL4J_ADD_VM_PARAMS -classpath "$local_classpath" install4j.Installer2990604421 "$@" Any pointers on how I might be able to upgrade ? Cheers, Tim

Liam, PortSwigger Agent | Last updated: Oct 08, 2021 08:28AM UTC

Thanks for your message, Tim. We'll look into the issue you are encountering. What happens when you attempt to use the plain JAR file?

Tim | Last updated: Oct 11, 2021 11:08PM UTC

Hi Liam, Yes - using the plain .jar works fine. That's my current workaround :-) Cheers,

You need to Log in to post a reply. Or register here, for free.