A fatal error has been detected by the Java Runtime Environment

2016-08-29 12:29:18,140 INFO [main] [org.mycontroller.standalone.StartApp:108] MyController.org server started in [15490] ms
2016-08-29 12:40:02,287 WARN [Thread-5] [org.mycontroller.standalone.operation.PushbulletUtils:97] Note push sending failed:ClientResponse(statusCode=400, errorMsg={"error":{"code":"invalid_param","type":"invalid_request","message":"The param 'email' has an invalid value.","param":"email","cat":"\u003e:3"},"error_code":"invalid_param"}, entity=null, success=false)]

**~13:51**
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x76871ce4, pid=702, tid=0x6d58b460
#
# JRE version: Java(TM) SE Runtime Environment (8.0_101-b13) (build 1.8.0_101-b13)
# Java VM: Java HotSpot(TM) Client VM (25.101-b13 mixed mode linux-arm )
# Problematic frame:
# V  [libjvm.so+0x477ce4]  ContiguousSpace::prepare_for_compaction(CompactPoint*)+0x9c
#
# Failed to write core dump. 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:
# /home/pi/mycontroller/bin/hs_err_pid702.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

hs_err_pid702.log

http://pastebin.com/U9fetXm2

[jkandasa]

@cimba007 cool, if we face this issue again we will think about it.

I am using java 1.8.0_101, only 36 versions newer then yours 😉

I do not meant that your are using old version 😉 I meant that particular version might have issue.

@Watchdog: Maybe this can be incorporated into the startup script? Start mycontroller and then do this again in a 60second loop. If calling ./stop you should issue stop command to mycontroller java AND stop command to the looping start script. Just a suggestion 😉

Yes, this should be nice one. I will think about this when I get time +1

[jkandasa]

@cimba007 reopen this ticket if you face this issue.