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 when indexing big sqlite DB files #758

Closed
bamthomas opened this issue Mar 1, 2021 · 0 comments
Closed

JVM crash when indexing big sqlite DB files #758

bamthomas opened this issue Mar 1, 2021 · 0 comments
Assignees

Comments

@bamthomas
Copy link
Collaborator

Describe the bug

When indexing big sqlite3 files the JVM crashes with a core dump.

To Reproduce
Steps to reproduce the behavior:

  1. create or download a big sqlite file
  2. index the file with either CLI or UI
  3. Datashare should crash with the following message
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000000000bb4e, pid=1, tid=0x00007f6f33ca9b10
#
# 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  0x000000000000bb4e
#
# Core dump written. Default location: /home/datashare/core or core.1
#
# An error report file with more information is saved as:
# /home/datashare/hs_err_pid1.log

Expected behavior

No crash.

Additional context

It may be related to uber/h3-java#25
And https://github.com/gliderlabs/docker-alpine/blob/master/docs/caveats.md

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

2 participants