HI Stephan, thanks very much for the response. Regarding the rj issue, it looks like it has been fixed with version 4.0.3_1, so no more problems there. Part of the issue was that the Java Framework has been moved in BigSur.
Regarding the SWT error, is there a way for me to catch a more useful report? This problem is specific to Eclipse 2021-12 and Statet 4.3.xxx.
I can still run Eclipse 2021-06 and StatEt 4.2.xxx. However, here there is an issue with the editor window not refreshing when entering a new line. Not a major issue, only moderately inconvenient.
I will try to get a java heap dump from eclipse. It is tricky because it requires tweaking the Info.plist file, not well documented. Will let you know if I succeed.
Thanks very much, - Andrea
Hi Andrea, [10.01.2021 15:40] Andrea Malagoli wrote: I am running Eclipse 2020-12 on MacOS BigSur 11.1.
I have install StatET 4.3.0.202012151020
When I try to run a simple graphics command, eg. plot(1:10), eclipse crashes.
Also note that rj rj.gd fail to compile out of the box and need tweaking of the config file.
What did you have to change? There is a bug related to the build for BigSur: https://gitlab.com/walware/de.walware.rj-server.gr/-/issues/10Please report on your experiences there, or if you had other problems, open a new issue https://gitlab.com/walware/de.walware.rj-server.gr/-/issues/new Concerning the crash: it looks like an issue in SWT. Unfortunately the crash report doesn't show the java stack trace, so it is difficult to figure out what went wrong. Thread 111 Crashed:: Java: R Engine 'R / RJ (Jan 10, 2021, 9:26:41 AM)'
0 libsystem_kernel.dylib 0x00007fff20323462 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff20351610 pthread_kill + 263
2 libsystem_c.dylib 0x00007fff202a4720 abort + 120
3 libjvm.dylib 0x0000000008014d51 os::abort(bool, void*, void const*) + 49
4 libjvm.dylib 0x00000000081ea6ec VMError::report_and_die(int, char const*, char const*, __va_list_tag*, Thread*, unsigned char*, void*, void*, char const*, int, unsigned long) + 2972
5 libjvm.dylib 0x00000000081e9b1c VMError::report_and_die(Thread*, unsigned int, unsigned char*, void*, void*, char const*, ...) + 156
6 libjvm.dylib 0x00000000081ea781 VMError::report_and_die(Thread*, unsigned int, unsigned char*, void*, void*) + 33
7 libjvm.dylib 0x0000000008019a2a JVM_handle_bsd_signal + 858
8 libjvm.dylib 0x000000000801681d signalHandler(int, __siginfo*, void*) + 45
9 libsystem_platform.dylib 0x00007fff20395d7d _sigtramp + 29
10 ??? 0xaaaaaaaaaaaaaaaa 0 + 12297829382473034410
11 com.apple.CoreGraphics 0x00007fff24f547dd CGBlt_fillBytes + 277
12 com.apple.CoreGraphics 0x00007fff24f544fb rgba32_mark + 18089
13 com.apple.CoreGraphics 0x00007fff24f4f7e1 RIPLayerBltShape + 1349
14 com.apple.CoreGraphics 0x00007fff24f4d8b6 ripc_Render + 328
15 com.apple.CoreGraphics 0x00007fff24f8e228 ripc_DrawPath + 425
16 com.apple.CoreGraphics 0x00007fff2526aa81 draw_path + 409
17 com.apple.CoreGraphics 0x00007fff24f8df98 CGContextDrawPath + 238
18 com.apple.AppKit 0x00007fff22ddf964 -[NSBezierPath fill] + 276
19 libswt-pi-cocoa-4940r23.jnilib 0x0000000029697c8d Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSend__JJ + 45
20 ??? 0x00000000197b7869 0 + 427522153
21 ??? 0x00000000133574b4 0 + 322270388
22 ??? 0x0000000011c3feea 0 + 298057450
23 ??? 0x0000000011c3feea 0 + 298057450
24 ??? 0x0000000011c3fb70 0 + 298056560
25 ??? 0x0000000011c3fc40 0 + 298056768
26 ??? 0x0000000011c3fd23 0 + 298056995
27 ??? 0x0000000011c3feea 0 + 298057450
28 ??? 0x0000000011c3ff2f 0 + 298057519
29 ??? 0x0000000011c3ff2f 0 + 298057519
30 ??? 0x0000000012a54c74 0 + 312822900
31 ??? 0x0000000011c3fc40 0 + 298056768
32 ??? 0x0000000011c3fd23 0 + 298056995
33 ??? 0x0000000011c3fc40 0 + 298056768
34 ??? 0x0000000011c3fd23 0 + 298056995
35 ??? 0x0000000011c3fd23 0 + 298056995
36 ??? 0x0000000011c3feea 0 + 298057450
37 ??? 0x0000000011c3feea 0 + 298057450
38 ??? 0x0000000011c3feea 0 + 298057450
39 ??? 0x0000000011c3feea 0 + 298057450
40 ??? 0x0000000011c3ff2f 0 + 298057519
41 ??? 0x0000000011c3feea 0 + 298057450
42 ??? 0x0000000011c3ff2f 0 + 298057519
43 ??? 0x0000000011c3feea 0 + 298057450
44 ??? 0x0000000011c3feea 0 + 298057450
45 ??? 0x0000000011c3feea 0 + 298057450
46 ??? 0x0000000011c3feea 0 + 298057450
47 ??? 0x0000000011c36949 0 + 298019145
48 libjvm.dylib 0x0000000007c98942 JavaCalls::call_helper(JavaValue*, methodHandle const&, JavaCallArguments*, Thread*) + 738
49 libjvm.dylib 0x0000000007c97829 JavaCalls::call_virtual(JavaValue*, Klass*, Symbol*, Symbol*, JavaCallArguments*, Thread*) + 489
50 libjvm.dylib 0x0000000007c978f3 JavaCalls::call_virtual(JavaValue*, Handle, Klass*, Symbol*, Symbol*, Thread*) + 99
51 libjvm.dylib 0x0000000007d43320 thread_entry(JavaThread*, Thread*) + 176
52 libjvm.dylib 0x00000000081851a2 JavaThread::thread_main_inner() + 178
53 libjvm.dylib 0x00000000081822b1 Thread::call_run() + 113
54 libjvm.dylib 0x0000000008014327 thread_native_entry(Thread*) + 407
55 libsystem_pthread.dylib 0x00007fff20351950 _pthread_start + 224
56 libsystem_pthread.dylib 0x00007fff2034d47b thread_start + 15
Maybe you can check the command line options of your JavaVM, if it is possible to enable a better/additional crash report; add the option(s) to the eclipse.ini file. Regards, Stephan
|
