komga: Fatal error detected by JRE on initial start (Debian armv7l)

Komga environment

  • OS: Debian GNU/Linux 10 (buster) armv7l
  • Komga version: 0.85.0
  • I am running Komga from the jar
    • Java version: OpenJDK Runtime Environment (11.0.9.1+1) (build 11.0.9.1+1-post-Debian-1deb10u2)
    • Launch command: java -Xmx384m -jar komga-0.85.0.jar

Describe the bug

Komga is unable to start, A fatal error has been detected by the Java Runtime Environment.

Steps to reproduce

  1. Download komga.jar
  2. Execute by command “java -Xmx384m -jar komga-0.85.0.jar”

Expected behavior

Komga to start successfully

Actual behavior

2021-03-30 11:51:06.842  INFO 3624 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2021-03-30 11:51:08.094  INFO 3624 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x95a00acc, pid=3624, tid=3625
#
# JRE version: OpenJDK Runtime Environment (11.0.9.1+1) (build 11.0.9.1+1-post-Debian-1deb10u2)
# Java VM: OpenJDK Server VM (11.0.9.1+1-post-Debian-1deb10u2, mixed mode, serial gc, linux-)
# Problematic frame:
# C  [webp-imageio-unknown-e015c1cd-cdc1-41c6-9725-209ea8a07495-libwebp-imageio.so+0x8acc]
#
# 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/komga/hs_err_pid3624.log
#
# If you would like to submit a bug report, please visit:
#   https://bugs.debian.org/openjdk-11
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted

Launch console dump

$ java -Xmx384m -jar komga-0.85.0.jar 
 ____  __.
|    |/ _|____   _____    _________
|      < /  _ \ /     \  / ___\__  \
|    |  (  <_> )  Y Y  \/ /_/  > __ \_
|____|__ \____/|__|_|  /\___  (____  /
        \/           \//_____/     \/

Version: 0.85.0

2021-03-30 11:50:14.480  INFO 3624 --- [           main] org.gotson.komga.ApplicationKt           : Starting ApplicationKt using Java 11.0.9.1 on code-server with PID 3624 (/opt/komga/komga-0.85.0.jar started by coder in /opt/komga)
2021-03-30 11:50:14.574  INFO 3624 --- [           main] org.gotson.komga.ApplicationKt           : No active profile set, falling back to default profiles: default
2021-03-30 11:50:44.053  INFO 3624 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@a68df9' of type [org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-03-30 11:50:44.138  INFO 3624 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'methodSecurityMetadataSource' of type [org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2021-03-30 11:50:49.250  INFO 3624 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2021-03-30 11:50:49.409  INFO 3624 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2021-03-30 11:50:49.410  INFO 3624 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.43]
2021-03-30 11:50:50.052  INFO 3624 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2021-03-30 11:50:50.054  INFO 3624 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 34600 ms
2021-03-30 11:50:54.356  INFO 3624 --- [           main] o.s.b.a.e.web.ServletEndpointRegistrar   : Registered '/actuator/jolokia' to jolokia-actuator-endpoint
2021-03-30 11:50:54.919  INFO 3624 --- [           main] io.hawt.HawtioContextListener            : Initialising hawtio services
2021-03-30 11:50:55.479  INFO 3624 --- [           main] io.hawt.system.ConfigManager             : Configuration will be discovered via system properties
2021-03-30 11:50:55.489  INFO 3624 --- [           main] io.hawt.jmx.JmxTreeWatcher               : Welcome to Hawtio 2.13.0
2021-03-30 11:50:55.606  INFO 3624 --- [           main] i.h.w.auth.AuthenticationConfiguration   : Starting hawtio authentication filter, JAAS realm: "karaf" authorized role(s): "admin,manager,viewer" role principal classes: ""
2021-03-30 11:50:58.059  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/home/coder/.komga/artemis/journal,bindingsDirectory=/home/coder/.komga/artemis/bindings,largeMessagesDirectory=/home/coder/.komga/artemis/largemessages,pagingDirectory=/home/coder/.komga/artemis/paging)
2021-03-30 11:50:58.387  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221013: Using NIO Journal
2021-03-30 11:50:59.055  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221057: Global Max Size is being adjusted to 1/2 of the JVM max size (-Xmx). being defined as 194,641,920
2021-03-30 11:50:59.180  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
2021-03-30 11:50:59.470  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601138: User anonymous@unknown is getting notification info on target resource: null []
2021-03-30 11:50:59.476  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.ActiveMQServerControlImpl@4ccef7 []
2021-03-30 11:50:59.478  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601138: User anonymous@unknown is getting notification info on target resource: ActiveMQServerImpl::serverUUID=274b8d5b-913c-11eb-8a42-0242ac110003 []
2021-03-30 11:50:59.838  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221034: Waiting indefinitely to obtain live lock
2021-03-30 11:50:59.840  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221035: Live Server Obtained live lock
2021-03-30 11:51:00.534  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.AddressControlImpl@1a3f4de []
2021-03-30 11:51:00.545  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.AddressControlImpl@1d2e270 []
2021-03-30 11:51:00.550  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.AddressControlImpl@195105b []
2021-03-30 11:51:00.554  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.AddressControlImpl@13e19b3 []
2021-03-30 11:51:00.985  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.QueueControlImpl@13a7ef5 []
2021-03-30 11:51:01.025  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.QueueControlImpl@851ce1 []
2021-03-30 11:51:01.059  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.QueueControlImpl@f6fd7f []
2021-03-30 11:51:02.157  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221080: Deploying address DLQ supporting [ANYCAST]
2021-03-30 11:51:02.198  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221003: Deploying ANYCAST queue DLQ on address DLQ
2021-03-30 11:51:02.274  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221080: Deploying address ExpiryQueue supporting [ANYCAST]
2021-03-30 11:51:02.276  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221003: Deploying ANYCAST queue ExpiryQueue on address ExpiryQueue
2021-03-30 11:51:02.279  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221003: Deploying ANYCAST queue tasks.background on address tasks.background
2021-03-30 11:51:02.712  INFO 3624 --- [           main] org.apache.activemq.audit.base           : AMQ601019: User anonymous@unknown is getting mbean info on target resource: org.apache.activemq.artemis.core.management.impl.AcceptorControlImpl@95416d []
2021-03-30 11:51:02.913  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221007: Server is now live
2021-03-30 11:51:02.914  INFO 3624 --- [           main] org.apache.activemq.artemis.core.server  : AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.15.0 [localhost, nodeID=274b8d5b-913c-11eb-8a42-0242ac110003] 
2021-03-30 11:51:06.842  INFO 3624 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2021-03-30 11:51:08.094  INFO 3624 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x95a00acc, pid=3624, tid=3625
#
# JRE version: OpenJDK Runtime Environment (11.0.9.1+1) (build 11.0.9.1+1-post-Debian-1deb10u2)
# Java VM: OpenJDK Server VM (11.0.9.1+1-post-Debian-1deb10u2, mixed mode, serial gc, linux-)
# Problematic frame:
# C  [webp-imageio-unknown-e015c1cd-cdc1-41c6-9725-209ea8a07495-libwebp-imageio.so+0x8acc]
#
# 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/komga/hs_err_pid3624.log
#
# If you would like to submit a bug report, please visit:
#   https://bugs.debian.org/openjdk-11
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted

coder@code-server:/opt/komga$ uname -a
Linux code-server 4.14.22-armada-18.09.3 #1 SMP Mon Dec 21 02:42:49 UTC 2020 ga-18.09.3 Build-24 armv7l GNU/Linux
coder@code-server:/opt/komga$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

Log file

hs_err_pid3624.log

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 35 (19 by maintainers)

Commits related to this issue

Most upvoted comments

awesome, thanks for confirming. I’ll ship that feature, and also try fixing the lib to disable it for armv7l.

Thanks for the report. I’ll do the necessary changes in the webp library and deliver a new Komga release to fix your problem, so you can use mainline releases.

@robco Does this still happen with the newly released 0.88.1, which replaces the native webp binaries with optimized Java implementations?

It does not replace the native lib, it replaces a java lib with another java lib.