Backendless Support
 
Waiting for user's response

Memory Increasing continuously with iOS app after changing from Parse

Hi,

We have recently changed from Parse to Backendless. Unfortunately, when we run the app the memory continuously increases until the app crashes, this was not the case before with Parse.

Best

Feras A.

Leave a Comment

Comments (16)

photo
2

Could you give us some your code, which demonstrates this issue?

photo
1

Thank you, I have attached some of the code to this message. Let me know if anything is unclear and we appreciate the help.

Best,

Feras A

photo
1

Please use Product->Profile Leaks instrument to find the points of memory problem.

photo
1

I have and there are many leaks. This is shown by looking into the allocations and not the leaks instrument (which only shows two small leaks). We are sure it is backendless as I have reverted the changes to Parse and the allocations no longer increase. I am unsure how to approach this?

photo
2

Could you provide the Backendless methods which are the causes of allocation? Maybe some screenshots from Allocations dashboard? We need to reproduce this issue.

photo
1

Hi, I have attached two allocations screenshots, highlighting the categories that are continuously increasing in the app. It is unclear which specific Backendless methods are causing them though. Memory is not being deallocated somewhere in the backendless code.

photo
1

How can we reproduce this issue? Which Backendless SDK calls are the causes of memory allocations? Could you provide some sample project which demonstrates this problem (here or to support@backendless.com)?

photo
1

Hi, Thank you for your message. I am trying to figure this out or figure out what to send you so that it can be resolved. Will come back to you soon.

Best,

Feras

photo
1

Hi,

Could you please clarify how backendless works with Xcode ARC?

Best,

Feras A.

photo
1

ARC is disabled in backendless libs:

4ca439c112e75d7bf3fcc10559531934

photo
photo
1

Hi,

Thanks for the quick reply. Can this be enabled?

Best

Feras A.

photo
1

It can be enabled, but some time for testing is needed.

photo
1

perfect, please let me know when I can enable it and how.

Best

Feras A.

photo
1

Hi,

We have some code that used to work fine in the Parse version. But with Backendless the memory is not being deallocated, for example the code:

- (void) stopLocationUpdate{

[self.m_locationManager stopUpdatingLocation];

}

is causing a memory leak, even though nothing has changed from when we were running it with Parse. This is an Apple function and so I don't understand what is happening. Could Backendless affect the functioning of ARC in the code not related to Backendless?

Best,

Feras A.

photo
1

I don't think that Backendless code can affect the functioning of ARC in Apple code, but we will investigate this problem. The internal task BKNDLSS-13457 is created.

photo
1

Thank you. I look forward to hearing back from you. F

photo