"We offer new support options and therefor the forums are now in read-only mode! Please check out our Support Center for more information." - Vuforia Engine Team

Ground plane runaway memory usage in iOS

By mustarddesign on Fri, 06/07/2019 - 10:35

HI,

I'm having problems with run-away memory usage whilst using ground plane in iOS. For a long time I thought it was my project, but I've now tried it on a blank project and the memory just keeps increasing.

This will continue until the device becomes unresponsive. Tested in Unity 2018.3.14, 2018.4.0, 2019.1.5 and vuforia 8.1.7 and 8.1.11. Occurs on iPhone 6, iPad Air 2 and iPad Pro. iOS 11 and iOS 12. Xcode 10.1.

If you stop and restart the positional device tracker it drops right back down then starts climbing again.

This is quite a rapid rise and can cause a device crash in about 30 seconds to a minute on lower memory devices. I'm pulling my hair out over this one as it is preventing us launching a client app.

This example project above consists of ARCamera, Plane Finder, Ground Plane Stage and a single primitive Cube.

Any ideas????

Many thanks,

Graham

Now I know why my app is

Now I know why my app is crashing on iOS after a while . . .

Hello,

Thanks for the report. We'll attempt to replicate.

-Vuforia Engine Support

Thank you, this is getting

Thank you, this is getting quite urgent for us as we have a fixed deadline for a launch in a few weeks time, so any help would be great.

Hello,

We believe we have fixed this issue in our upcoming commercial release (soon).

Our recommendations for working around this issue are:

Thank you, I will try this

Thank you, I will try this out over the next couple of days and report back any further issues.

Thanks @mustarddesign.

Thanks @mustarddesign. Looking forward to your feedback.

-Vuforia Engine Support

In my initial testing it

In my initial testing it seems to be massively improved. There is still a gradual increase in memory (although I haven't proven this isn't an unrelated memory leak), but no where near the steep climb we were seeing before.

Many thanks,

Graham

We have found that the

We have found that the runaway memory usage doesn't happen now in the new version of Vuforia, as long as you wait for Initializing to go the *first time*. If you call reset and it goes to initialising again then the run away memory usage doesn't appear to occur.

Hello @mustarddesign,

A follow up to this, we have

A follow up to this, we have tried it with the latest version of vuforia and see the same issues if we don't wait for it to no longer return initialising.