This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-19
Channels
- # announcements (6)
- # aws (10)
- # beginners (73)
- # bristol-clojurians (2)
- # calva (9)
- # cider (25)
- # clj-kondo (7)
- # clojure (160)
- # clojure-dev (2)
- # clojure-europe (63)
- # clojure-italy (7)
- # clojure-nl (10)
- # clojure-uk (76)
- # clojuredesign-podcast (6)
- # clojurescript (63)
- # cursive (6)
- # data-science (3)
- # datomic (26)
- # duct (59)
- # emacs (1)
- # fulcro (12)
- # graalvm (17)
- # hoplon (23)
- # jobs-discuss (2)
- # kaocha (6)
- # meander (7)
- # off-topic (3)
- # pathom (2)
- # rdf (68)
- # re-frame (12)
- # reagent (20)
- # reitit (5)
- # ring (3)
- # ring-swagger (1)
- # shadow-cljs (14)
- # spacemacs (10)
- # sql (3)
- # tools-deps (30)
- # yada (9)
Hello everyone! Recently I’ve been trying to compile a clojure project with graalvm, and I’ve been facing class initialization errors both on runtime and buildtime. I was wondering if anyone could help 😅
I got this
Original exception that caused the problem: org.graalvm.compiler.code.SourceStackTraceBailoutException$1: unbalanced monitors: mismatch at monitorexit, 3|LoadField#lockee__5436__auto__ != 96|LoadField#lockee__5436__auto__
when trying to compile the binary using verbose and printing error stacks@m.amarnah Can you try again with clojure 1.10.2-alpha1?
it has to do with the locking macro. if thread pools use that locking macro, then indirectly, potentially related
So I think that fixed the mismatch monitorexit problem. It was showing Error: Unsupported features in 3 methods
and now it says 2 methods instead of 3.
The thing is down the stack trace I found this Caused by:
Just a side note, I’m importing native java libraries in my clojure code.
(:import [java.util.concurrent Executors ExecutorService TimeUnit])
although I tried importing that in a hello world project and it worked just fine.
@m.amarnah why does your code try to load a project.clj file?