Home Forums Software Development Random crash during calibration-Gaze SDK

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #3375
    Jenna Wise
    Participant

    I am working on an eye-tracking plug-in for eclipse. We are adding support for the Tobii EyeX Controller and the plug-in has full control over starting and stopping tracking and calibration and so forth.
    The plug-in is written in Java and we are using C++ jni to call the Gaze SDK functions.

    The calibration starts fine, but at random intervals of adding new calibration points the Java Runtime Environment ecounters a fatal error:

    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6b781da9, pid=5288, tid=6676
    #
    # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
    # Java VM: Java HotSpot(TM) Client VM (24.45-b08 mixed mode, sharing windows-x86 )
    # Problematic frame:
    # C [libEyeXTracker.dll+0x1da9]
    #
    # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
    #
    # If you would like to submit a bug report, please visit:
    # http://bugreport.sun.com/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    #

    Here is the stack trace:
    Stack: [0x010f0000,0x01140000], sp=0x0113f940, free space=318k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    C [libEyeXTracker.dll+0x1da9]
    j edu.ysu.itrace.trackers.EyeXTracker$Calibrator.jniAddPoint(DD)V+0
    j edu.ysu.itrace.trackers.EyeXTracker$Calibrator.useCalibrationPoint(DD)V+3
    j edu.ysu.itrace.Calibrator.calibrate()V+159
    j edu.ysu.itrace.trackers.EyeXTracker.calibrate()V+4
    j edu.ysu.itrace.trackers.EyeXTracker.main([Ljava/lang/String;)V+82
    v ~StubRoutines::call_stub
    V [jvm.dll+0x13f1fa]
    V [jvm.dll+0x202aee]
    V [jvm.dll+0x13f27d]
    V [jvm.dll+0xc9945]
    V [jvm.dll+0xd45e7]
    C [javaw.exe+0x2070]
    C [javaw.exe+0xa5b1]
    C [javaw.exe+0xa63b]
    C [KERNEL32.DLL+0x17c04]
    C [ntdll.dll+0x5ad1f]
    C [ntdll.dll+0x5acea]

    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    j edu.ysu.itrace.trackers.EyeXTracker$Calibrator.jniAddPoint(DD)V+0
    j edu.ysu.itrace.trackers.EyeXTracker$Calibrator.useCalibrationPoint(DD)V+3
    j edu.ysu.itrace.Calibrator.calibrate()V+159
    j edu.ysu.itrace.trackers.EyeXTracker.calibrate()V+4
    j edu.ysu.itrace.trackers.EyeXTracker.main([Ljava/lang/String;)V+82
    v ~StubRoutines::call_stub

    Now the calibration UI is being run by the main thread and the main thread is forced to wait until the add_calibration_point_handler callback function is invoked and finishes before trying to call tobiigaze_calibration_add_point_async again (ie. waiting until the tracker is done with the current point to move to the next point).

    I have narrowed the error down to the tobiigaze_calibration_add_point_async function call. It does not reach the callback function before crashing.
    Also as I said before, it crashes randomly meaning that sometimes it will crash when adding the second calibration point and then sometimes it will crash when adding the fourth calibration point and so forth.

    Also the EyeX Engine is not activated so it will not overwrite any calibration data.

    Please, let me know what you think the issue might be or if you need any other information.
    I do believe that our repository is now public on github, so feel free to take a look.
    https://github.com/YsuSERESL/iTrace
    The current EyeX code is under the gazeSDK branch.

    Thanks!
    Jenna

    #3376
    Jenna Wise
    Participant

    The problem was that I was sending tobiigaze_point_2d* point to the tobiigaze_calibration_add_point function instead of a reference to tobiigaze_point_2d point. It is working perfectly fine now.

    #3394
    Jenny [Tobii]
    Participant

    Hi Jenna,
    I’m glad you found the root cause and that everything is working fine now!

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.