Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JVM crash on alpine linux #43

Open
kklorenzotesta opened this issue Jan 27, 2020 · 2 comments
Open

JVM crash on alpine linux #43

kklorenzotesta opened this issue Jan 27, 2020 · 2 comments

Comments

@kklorenzotesta
Copy link

kklorenzotesta commented Jan 27, 2020

Using the version 1.4.13 on alpine linux cause the java runtime to crash, with version 1.4.12 works fine. This is a minimal repository reproducing the bug: repository

Running docker-compose up in the repository starts a docker container with openjdk:8-alpine that runs sbt assets. This cause the jvm to fail with the following message:

[info] Loading settings for project workingdir-build from metals.sbt,plugins.sbt ...
[info] Loading project definition from /workingDir/project
[info] Loading settings for project root from build.sbt ...
[info] Set current project to Bug (in build file:/workingDir/)
[info] Sass compiling on 1 source(s)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000000b71d6, pid=1, tid=0x00007f8509fa9b10
#
# JRE version: OpenJDK Runtime Environment (8.0_212-b04) (build 1.8.0_212-b04)
# Java VM: OpenJDK 64-Bit Server VM (25.212-b04 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 3.12.0
# Distribution: Custom build (Sat May  4 17:33:35 UTC 2019)
# Problematic frame:
# C  0x00000000000b71d6
#
# Failed to write core dump. 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:
# /workingDir/hs_err_pid1.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   https://icedtea.classpath.org/bugzilla
#

Here is the full error report file:
hs_err_pid1.log

@irundaia
Copy link
Owner

Hmm typically this is caused by a memory issue in libsass itself. I’ll have a look at whether this issue can be solved by upgrading libsass, if not, I’ll report it upstream.

Thanks for letting me know!

@mgladdish
Copy link

Any progress? I've just hit this same issue with 1.5.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants