List
Instant Tracker Crash
Posted Date: 2019-05-10 13:40     Edited Date: 2019-05-14 4:06     Writer: inactive

1. SDK Version: 4.1.1
2. Development Environment: Unity-Android (Unity 2019.1.1f1, IL2CPP, arm64v8a)
3. Tracker/Scanner: Instant Tracker
4. License Type: Free
5. Target Device(Optional): Wiko Wim lite (Android 7.1.1)

Hi !

I encounter an issue today that might be linked to Unity 2019 while using the Instant Tracker sample: 

2019-05-10 15:23:59.167 18035-18233/? E/CRASH: pid: 18035, tid: 18233, name: UnityMain  >>> com.testcompany.testapp <<<
2019-05-10 15:23:59.331 18035-18064/? E/AndroidRuntime: FATAL EXCEPTION: UnityMain
    Process: com.testcompany.testapp , PID: 18035
    java.lang.Error: FATAL EXCEPTION [UnityMain]
    Unity version     : 2019.1.1f1
    Device model      : WIKO WIM Lite
    Device fingerprint: WIKO/p6901/p6901:7.1.1/NMF26F/androi04211336:user/release-keys
    
    Caused by: java.lang.Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000000000ec
    Build fingerprint: 'WIKO/p6901/p6901:7.1.1/NMF26F/androi04211336:user/release-keys'
    Revision: '0'
    pid: 18035, tid: 18233, name: UnityMain  >>> com.testcompany.testapp  <<<
        x0   0000000000000000  x1   0000007fa906b9f4  x2   0000007fa906b9f0  x3   0000007f733f2c40
        x4   0000000000000000  x5   0000000000000000  x6   0000007fb4e45000  x7   0000000000000000
        x8   00000000bd800000  x9   0000000000000002  x10  0000000000000001  x11  0000000000000000
        x12  000000000000a5de  x13  00000000000019c0  x14  000000000000000c  x15  2e8ba2e8ba2e8ba3
        x16  0000007f75b165b0  x17  0000007f74a986f8  x18  0000000000000006  x19  0000007f733eb410
        x20  0000007f73e681c0  x21  0000007f733f2b48  x22  0000000000000000  x23  0000007fb2c48ed8
        x24  0000007fa906c4e8  x25  0000007f73189788  x26  00000000000000f8  x27  0000000000000128
        x28  0000007f76b7c2a0  x29  0000007fa906bba0  x30  0000007f74b15380
        sp   0000007fa906b9c0  pc   0000007f74b1543c  pstate 0000000020000000
    
        at [vdso].(:0)
        at libMaxstAR._ZN7maxstAR10VIOTracker25prepareEmergencySituationEPNS_5FrameE(_ZN7maxstAR10VIOTracker25prepareEmergencySituationEPNS_5FrameE:948)
        at libMaxstAR._ZN7maxstAR10VIOTracker7processEPNS_5FrameE(_ZN7maxstAR10VIOTracker7processEPNS_5FrameE:228)
        at libMaxstAR._ZN7maxstAR12InstantLogic8trackingEPNS_5FrameE(_ZN7maxstAR12InstantLogic8trackingEPNS_5FrameE:24)
        at libMaxstAR._ZN7maxstAR7IOLogic10trackFrameEPhPf(_ZN7maxstAR7IOLogic10trackFrameEPhPf:280)
        at libMaxstAR._ZN7maxstAR14InstantTracker10trackFrameEPhPf(_ZN7maxstAR14InstantTracker10trackFrameEPhPf:52)
        at libMaxstAR._ZN7maxstAR9ARManager20trackingThreadWorkerEPv(_ZN7maxstAR9ARManager20trackingThreadWorkerEPv:1032)
        at libMaxstAR.(:0)
        at libc._ZL15__pthread_startPv(_ZL15__pthread_startPv:196)
        at libc.__start_thread(__start_thread:16)

 

It didn't happen immediately, it happened after while when moving around the maxst cube. I will probably try on other devices to check if the issue is specific.

Thank,

Pierre 

 

Posted Date: 2019-05-13 5:21     Edited Date: 2019-05-13 5:21     Writer: inactive

Our SDK does not yet support Unity 2019 version. Please describe in detail the circumstances under which the problem you raised is occurring. We will review it for updates to the Unity 2019 version. Does the problem occur when you simply run the sample code we provide?

 

Leo

Maxst Support Team

Posted Date: 2019-05-13 7:27     Edited Date: 2019-05-13 7:27     Writer: inactive

Thank you for your prompt reply.

I'm using pretty much the same code as the sample provided. The error doesn't occur right away: It is occuring randomly after a few seconds. I tested on several devices (Wiko Wim lite // Android 7.1.1, Honor 8 Pro // Android 8.0) and also tested 2 architectures (arm64-v8a and armeabi-v7a). 

(Here you can find the modified one I used)

// call at first        
void Start()
        {
            instantTrackable = FindObjectOfType<InstantTrackableBehaviour>();
            if (instantTrackable == null)
            {
                return;
            }

            instantTrackable.OnTrackFail();
            StartCamera();

            /*TrackerManager.GetInstance().SetTrackingOption(TrackerManager.TrackingOption.EXTEND_TRACKING);
            TrackerManager.GetInstance().SetTrackingOption(TrackerManager.TrackingOption.ENHANCED_MODE);
            TrackerManager.GetInstance().SetTrackingOption(TrackerManager.TrackingOption.JITTER_REDUCTION_ACTIVATION);*/


            TrackerManager.GetInstance().StartTracker(TrackerManager.TRACKER_TYPE_INSTANT);

            SensorDevice.GetInstance().Start();
        }


// Call later when the user press a button
        public void StartPlane()
        {
            TrackerManager.GetInstance().FindSurface();
            findSurfaceDone = true;
            touchSumPosition = Vector3.zero;
        }


// the Update function
        void Update()
        {
            if (instantTrackable == null)
            {
                return;
            }

            TrackingState state = TrackerManager.GetInstance().UpdateTrackingState();

            cameraBackgroundBehaviour.UpdateCameraBackgroundImage(state);

            hasFindTarget = true;

            if (!findSurfaceDone)
            {
                return;
            }
            
            TrackingResult trackingResult = state.GetTrackingResult();

            if (trackingResult.GetCount() == 0)
            {
                instantTrackable.OnTrackFail();
                return;
            }

            Trackable trackable = trackingResult.GetTrackable(0);
            Matrix4x4 poseMatrix = trackable.GetPose() * Matrix4x4.Translate(touchSumPosition);
            instantTrackable.OnTrackSuccess(trackable.GetId(), trackable.GetName(), poseMatrix);
        }

Thank you Pierre
Posted Date: 2019-05-13 8:38     Edited Date: 2019-05-13 8:38     Writer: inactive

Thank you for reporting bugs. When we update to support the Unity 2019 version, we will review and test the bug and incorporate it into the update.

 

Leo

Maxst Support Team

Posted Date: 2019-05-13 8:41     Edited Date: 2019-05-13 8:41     Writer: inactive

Thank you for your answer.

I will wait for the update and then comment this topic again with logs if the issue is still happening with the 2019 update.

Pierre

Posted Date: 2019-05-14 4:06     Edited Date: 2019-05-14 4:06     Writer: inactive

Thank you again.

 

Leo

Maxst Support Team