This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-24
Channels
- # announcements (3)
- # aws (5)
- # babashka (10)
- # beginners (61)
- # calva (22)
- # clara (9)
- # clj-kondo (8)
- # cljdoc (8)
- # cljsrn (15)
- # clojure (44)
- # clojure-australia (2)
- # clojure-europe (31)
- # clojure-hungary (20)
- # clojure-nl (5)
- # clojure-uk (3)
- # core-logic (2)
- # cursive (2)
- # data-science (2)
- # datalevin (4)
- # datascript (6)
- # datomic (17)
- # defnpodcast (1)
- # figwheel-main (1)
- # fulcro (18)
- # graalvm (2)
- # introduce-yourself (2)
- # jobs (1)
- # jobs-discuss (59)
- # lsp (44)
- # music (1)
- # nrepl (2)
- # off-topic (26)
- # pedestal (2)
- # re-frame (12)
- # reagent (27)
- # releases (1)
- # remote-jobs (4)
- # rewrite-clj (2)
- # sci (12)
- # shadow-cljs (12)
- # sql (10)
- # uncomplicate (6)
- # vim (12)
- # xtdb (2)
using datalevin 0.5.27 I run a job to copy and compress some xml values from one datalevin db to another datalevin db. During copying I run a few times
dtlv -d test2.lmdb -a stat
and I manage to crash the app doing the copying with this.
It happens consistently.
Is this expected?
cat /etc/debian_version
bookworm/sid
apt-cache show liblmdb0
Package: liblmdb0
Source: lmdb
Version: 0.9.24-1
Installed-Size: 104
I can share jvm dump probably but erhaps privatly
WARNING: All illegal access operations will be denied in a future release
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007f325b9ddd8d, pid=489175, tid=489277
#
# JRE version: OpenJDK Runtime Environment 18.9 (11.0.12+7) (build 11.0.12+7)
# Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.12+7, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [lmdbjava-native-library-12939233817828088453.so+0x5d8d] mdb_page_alloc.isra.19+0x44d
#
# Core dump will be written. Default location: Core dumps may be processed with "/lib/systemd/systemd-coredump %P %u %g %s %t 9223372036854775808 %h" (or dumping to workspace/core.489175)
Probably the stat command is not implemented properly for concurrent use case like this, could you file an issue? thanks.