iOS Question Show available memory in b4i?

[Vern]

Is there a way in b4i to show available memory? I want to compare memory usage for each page to detect memory leaks.

 

[Erel]

Do you get an error? If not then don't waste too much time on this.

App not starting on iPhone 4s and 6+

Hi all I have an app that does not start on the 4S and 6+ - it is fine on the other iPhone versions. It also works on the emulator too - for all versions. The splash screen shows and then the app stops and exists. The splash screen is called in Activity_Create. I have added a try catch block...

www.b4x.com

 

[Vern]

Users are having to restart their phones every 2 days to clear memory so yes, there's an issue. Is there any way to display available memory so we can detect where there are memory leaks?

 

[Erel]

There is no such thing. Your app cannot leak the phone memory. Killing the app will always return the consumed memory to the OS. If your app has a memory leak then it will eventually crash.

 

[Semen Matusovskiy]

os_proc_available_memory in os framework (ios 13+). But results maybe not the same, as you expect.

Example.

    Dim noMe As NativeObject = Me   
    Log (noMe.RunMethod ("getAvailableMemory", Null).AsNumber)

OBJC:

#If OBJC
#import <os/proc.h>
- (size_t) getAvailableMemory { return os_proc_available_memory; }
#End If

 

[Vern]

Apple directed us to these docs:

Finding Memory Leaks

Guidelines for improving the performance of memory-related code.

developer.apple.com

Gathering information about memory use | Apple Developer Documentation

Identify memory-use inefficiencies by measuring and profiling your app.

developer.apple.com

Reducing your app’s memory use | Apple Developer Documentation

Improve your app’s performance by analyzing memory-use metrics and making changes to maximize memory efficiency.

developer.apple.com

Investigating memory access crashes | Apple Developer Documentation

Identify crashes that arise from memory access issues, and investigate the cause of the crash.

developer.apple.com

We were looking for a way in b4i to track down the issue.