Out of memory error - twice!

Something has broken in my development environment.

The build of my watch app is successful and the app loads in the simulator but, with the app running in the simulator, the console reports:

Error: Out Of Memory Error

Details: Failed loading applicationFailed loading application

Out Of Memory Error

That's a direct copy: two "Out of Memory.." errors

The sim is reporting Mem:90/124.0 with Peak Memory 96.0kB, so that's not a problem.

Thereafter the app misbehaves in unaccountable ways. On a device when I run the app (no crash) I get an Out of Memory error in the app log.

The Out of Memory error started to appear last week, but I am not sure of event may have preceded it, but I can't recall any significant env changes. The last SDK or Eclipse update was some weeks ago.

Mac Mojave 10.14.6

Eclipse Version: 2019-06 (4.12.0)

SDK 3.0.12

There's something broken below decks but I don't know where to look.

0 peterdedecker over 5 years ago

Do you use backgrounding in this app? It could out of memory there

0 Alan.raceQs over 5 years ago in reply to peterdedecker

No, but that's the problem. Somehow I have set the background permission the manifest.

I found it by successively applying changes since the last clean run, you did it by wisdom.

Thanks.

0 peterdedecker over 5 years ago in reply to Alan.raceQs

hmm, glad it solves this for you, but surely it's worth a bug report if your app out of memories without having a background task. The permission an sich shouldn't cause this overhead imho.

0 jim_m_58 over 5 years ago in reply to peterdedecker

There's a bug report on this already:

https://forums.garmin.com/developer/connect-iq/i/bug-reports/setting-the-background-permission-in-an-app-that-doesn-t-have-a-background-process-can-cause-out-of-memory-errors-when-running-in-the-sim-3-0-11

0 peterdedecker over 5 years ago in reply to jim_m_58

the bug report mentions sim only, but it's also misbehaving on the real device, so it would be worth to add this info and/or to just link to this thread.

0 jim_m_58 over 5 years ago in reply to peterdedecker

Yes it will happen on real devices. it gets back to onAppInstall/onAppUpdate, where without any background annotation, it attempts to load the entire app as a background process twice at startup, but is really something that can be caught in the sim, so never seen on a real device, as the simple solution is not having background permissions if you don't need it. Catching it in the sim would be a much faster fix than having all the device FW handle it.

0 DaveBrillhart 4 days ago

Still a bug. If you have the background permission set but no BG processing, you'll get an Out of Memory error when running it in VSC

0 jim_m_58 4 days ago in reply to DaveBrillhart

If you have the background permission, when the app starts, onAppUpdate/onAppInstall runs in the background, even if you don't override them, So it tries to load your entire app if you have no annotations.

Remove the permission or add an annotation.

Why do you have the permission if you don't use a background service in your code?

You could try adding the background annotation to your AppBase class. That might be enough...