javaterminal / TerminalFX

Java FX Terminal Emulator
MIT License
277 stars 52 forks source link

Getting error when using TerminalFX with clojure #22

Open zcaudate opened 5 years ago

zcaudate commented 5 years ago

I can download and run the project fine. However, when I use maven to load it into a clojure project. There is an error. I don't think it's a clojure problem but I'm a bit stumped as to what to do.

boot.user=> (com.kodedu.terminalfx.TerminalAppStarter/main (make-array String 0))

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000010f1ecd9a, pid=47620, tid=206351
#
# JRE version: OpenJDK Runtime Environment (11.0+28) (build 11+28)
# Java VM: OpenJDK 64-Bit Server VM (11+28, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)
# Problematic frame:
# V  [libjvm.dylib+0x3ecd9a]  jni_CallStaticVoidMethodV+0xdf
#
# 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:
# /Users/chris/Development/caudata/kmi/hs_err_pid47620.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
zcaudate commented 5 years ago
---------------  S U M M A R Y ------------

Command Line: -Dboot.app.path=/usr/local/bin/boot /usr/local/bin/boot cider-fx

Host: MacBookPro13,1 x86_64 2000 MHz, 4 cores, 8G, Darwin 18.2.0
Time: Wed May 15 23:00:56 2019 CST elapsed time: 20 seconds (0d 0h 0m 20s)

---------------  T H R E A D  ---------------

Current thread (0x00007fdf67ba5000):  JavaThread "Thread-35" daemon [_thread_in_vm, id=9219, stack(0x0000700005497000,0x0000700005517000)]

Stack: [0x0000700005497000,0x0000700005517000],  sp=0x0000700005516680,  free space=509k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.dylib+0x3ecd9a]  jni_CallStaticVoidMethodV+0xdf
C  [libjfxwebkit.dylib+0x1bae566]  JNIEnv_::CallStaticVoidMethod(_jclass*, _jmethodID*, ...)+0x86
C  [libjfxwebkit.dylib+0x1bae4ac]  WTF::scheduleDispatchFunctionsOnMainThread()+0x17c
C  [libjfxwebkit.dylib+0x1682a25]  WTF::Function<void ()>::CallableWrapper<WebCore::DataURLDecoder::decode(WebCore::URL const&, WebCore::DataURLDecoder::ScheduleContext const&, WTF::Function<void (std::optional<WebCore::DataURLDecoder::Result>)>&&)::$_0>::call()+0x215
C  [libjfxwebkit.dylib+0x1bb1078]  WTF::BlockPtr<void ()> WTF::BlockPtr<void ()>::fromCallable<WTF::WorkQueue::dispatch(WTF::Function<void ()>&&)::$_0>(WTF::WorkQueue::dispatch(WTF::Function<void ()>&&)::$_0)::'lambda'(void*)::__invoke(void*)+0x48
C  [libdispatch.dylib+0x2d53]  _dispatch_call_block_and_release+0xc
C  [libdispatch.dylib+0x3dcf]  _dispatch_client_callout+0x8
C  [libdispatch.dylib+0xa124]  _dispatch_lane_serial_drain+0x26a
C  [libdispatch.dylib+0xabdc]  _dispatch_lane_invoke+0x184
C  [libdispatch.dylib+0x13090]  _dispatch_workloop_worker_thread+0x25b
C  [libsystem_pthread.dylib+0x260b]  _pthread_wqthread+0x199
C  [libsystem_pthread.dylib+0x2405]  start_wqthread+0xd

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000000

Register to memory mapping:

RAX=0x00007000055166c8 is pointing into the stack for thread: 0x00007fdf67ba5000
RBX=0x00007fdf67ba5000 is a thread
RCX=0x00007fdf6e54d398 points into unknown readable memory
RDX=0x0 is NULL
RSP=0x0000700005516680 is pointing into the stack for thread: 0x00007fdf67ba5000
RBP=0x0000700005516730 is pointing into the stack for thread: 0x00007fdf67ba5000
RSI=0x0 is NULL
RDI=0x00007fdf67ba5340 points into unknown readable memory
R8 =0x0 is NULL
R9 =0x0 is NULL
R10=0x0000000100000000 is an unknown value
R11=0x0 is NULL
R12=0x00000001322424b0: jvm+0 in /Users/chris/.openjfx/cache/11.0.1/libjfxwebkit.dylib at 0x000000012eba7000
R13=0x0 is NULL
R14=0x0 is NULL
R15=0x00007fdf67ba5340 points into unknown readable memory
rahmanusta commented 5 years ago

May it be a JavaFx or clojure bug?

zcaudate commented 5 years ago

I’m not exactly sure. It seems like there is a problem when calling Webview.

ashokkumarvel commented 4 years ago

https://github.com/javaterminal/TerminalFX/issues/33

Help !!!

rahmanusta commented 4 years ago

@ashokkumarvel @poorvajappja @PradeepSimba Please stop the mess. I answered your questions on individual issues.