Exporting a PDF File with the Insight Macro Enabled Causes Confluence to Crash

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

The Confluence service may crash when exporting a page as a PDF if the app Insight for Confluence version1.6.3 is enabled.

Environment

Confluence server and Data Center version 7.4.3

Insight for Confluence version1.6.3

Diagnosis

A Fatal Java error appears in the catalina.out file:

1 2 3 4 5 6 7 8 9 10 11 12 13 # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0x00007fa8eb3f0a19, pid=17112, tid=21843 # # JRE version: OpenJDK Runtime Environment (11.0.7+10) (build 11.0.7+10) # Java VM: OpenJDK 64-Bit Server VM (11.0.7+10, mixed mode, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # C [libj2v8_linux_x86_64.so+0xae3a19] v8::base::OS::Abort()+0x9 # # 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: # /opt/atlassian/confluence/bin/hs_err_pid17112.log

After reviewing the hs_err_pid log that was generated, we can see that Insight for Confluence by Mindville is referenced here:

1 2 3 4 5 6 7 8 9 10 11 12 13 C [libj2v8_linux_x86_64.so+0x5427f0] v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*, bool)+0x120 C [libj2v8_linux_x86_64.so+0x4996f7] v8::Script::Run(v8::Local<v8::Context>)+0x137 C [libj2v8_linux_x86_64.so+0x4a4fb4] v8::Script::Run()+0x34 C [libj2v8_linux_x86_64.so+0x3f687a] runScript(v8::Isolate*, JNIEnv_*, v8::Local<v8::Script>*, v8::TryCatch*, v8::Local<v8::Value>&, long)+0x37 C [libj2v8_linux_x86_64.so+0x3f78df] Java_com_eclipsesource_v8_V8__1executeStringScript+0x255 j com.eclipsesource.v8.V8._executeStringScript(JLjava/lang/String;Ljava/lang/String;I)Ljava/lang/String;+0 j com.eclipsesource.v8.V8.executeStringScript(JLjava/lang/String;Ljava/lang/String;I)Ljava/lang/String;+7 j com.eclipsesource.v8.V8.executeStringScript(Ljava/lang/String;Ljava/lang/String;I)Ljava/lang/String;+16 j com.eclipsesource.v8.V8.executeStringScript(Ljava/lang/String;)Ljava/lang/String;+4 j com.mindville.confluence.plugins.insight.export.ExportRenderer.render(Ljava/util/Map;)Ljava/lang/String;+676 j com.mindville.confluence.plugins.insight.InsightObjectsMacro.execute(Ljava/util/Map;Ljava/lang/String;Lcom/atlassian/confluence/content/render/xhtml/ConversionContext;)Ljava/lang/String;+186 v ~StubRoutines::call_stub V [libjvm.so+0x88d369] JavaCalls::call_helper(JavaValue*, methodHandle const&, JavaCallArguments*, Thread*)+0x3b9

Cause

This was tracked in JSDSERVER-7387 - Insight Macro for Confluence causes JVM crash

Solution

Fixed in Insight Macro for Confluence 1.6.9.

Updated on February 27, 2025

Still need help?

The Atlassian Community is here for you.