List
Image trackable behavior memory leak/bugs
Posted Date: 2018-11-04 9:57     Edited Date: 2018-11-07 1:22     Writer: inchkiev

Please provide your development details as below;

1. SDK Version: 4
2. Development Environment: Unity-Android, Unity-iOS
3. Tracker/Scanner:
4. License: Pro-Subscription

Good afternoon, our company has been using your SDK, but we are constantly confronted with various bugs.
First, if there is more than one trigger on the scene, content periodically appears on the screen (the camera doesn’t trigger the trigger)
Secondly, if you look at the profiler, then when you hover over a trigger, too much memory is spent, we assume this is due to the fact that you create each frame of the array with the objects in class ImageTrackableBehaviour.cs
Also, you have not had updates for a long time.

Posted Date: 2018-11-06 5:21     Edited Date: 2018-11-06 5:21     Writer: kscho

Hello.

Thanks for your interest in MAXST SDK.

We're looking into the second issue and we'll let you know as soon as we get something.

And we'll update our SDK to fix some bugs today and have a plan to release in v. 4.1.0 in the next month.

Thanks.

 

John,

MAXST Support Team

Posted Date: 2018-11-06 5:37     Edited Date: 2018-11-06 5:37     Writer: kscho

Hello.

We are not clear about what you mean.

I hope that you check my understanding of the first issue and let me clear the second issue.

1) When the camera point at the surrounding environment not including your targets, a certain target is sometimes recognized? Am I right?

2) Did you mean that the image tracker uses a lot of memory or Did you mean the image tracker leaks some memory continually?

 

Thanks.

 

John,

MAXST Support Team

 

Posted Date: 2018-11-06 15:54     Edited Date: 2018-11-06 15:54     Writer: inchkiev

1)  this is what happens, I still think this is because that recognition works all the time, and has no events


2) that the image tracker is constantly flowing in memory

Posted Date: 2018-11-07 1:22     Edited Date: 2018-11-07 1:22     Writer: kscho

Thanks for your answer.

Could you send us the short video which takes the first issue? We couldn't understant exactly what you mean so far.

And we couldn't detect memory leak during our test about the second issue.

Could you let us know how to detect the memory leak?

Thanks in advance.

 

John,

MAXST Support Team