Memory Warnings on App using 60 MB of RAM - only on iPhone 6+

Hey there guys.
Here is the problem. I recently had to switch from Mono to IL2CPP probably like everyone else.
Since then I’m seeing a strange behaviour.

My Game is using only 60mb or ram and yet when I launch a video from AdColony this results in imediate memory warnings and a crash shortly after. I checked with the Xcode Memory tool and it doesn’t even go that high up when AdColony launches one of their videos (something like from 60mb usage to 65-70mb )
The weird thing is that it only happens so on an iPhone 6+. It works fine on everything else i’ve tested it on.

Two questions here :

  1. Why would an app using less than 80 mb of ram result in memory warnings on an iPhone 6+? (I also have to say that I tested this on my 6+ while having EVERYTHING else removed, so this was the only process running)
  2. Does anyone else have similar problems?

Here is a typical log from the moment the app crashes :

2015-07-03 21:37:48.446 arrow[257:25437] Communications error: <OS_xpc_error: <error: 0x198840a80> { count = 1, contents =

“XPCErrorDescription” => <string: 0x198840e78> { length = 22, contents = “Connection interrupted” }

}>

2015-07-03 21:37:48.579 arrow[257:24922] Received memory warning.

WARNING → applicationDidReceiveMemoryWarning()

2015-07-03 21:37:48.694 arrow[257:24922] Received memory warning.

WARNING → applicationDidReceiveMemoryWarning()

2015-07-03 21:37:48.713 arrow[257:24922] Received memory warning.

WARNING → applicationDidReceiveMemoryWarning()

2015-07-03 21:37:48.733 arrow[257:24922] Received memory warning.

WARNING → applicationDidReceiveMemoryWarning()

2015-07-03 21:37:48.753 arrow[257:24922] Received memory warning.

WARNING → applicationDidReceiveMemoryWarning()

Seeing a similar thing here on 5.3…seems if a particularly large asset bundle is loaded/cached, the thread is stalled and this error/warning pops up…have it on both Mono and IL2CPP…we get a rare crash right around this point when we load our app first time …then on subsequent launches it is fine…

Hi Toolism did you ever find out what was happening? We have the same exact error on iphone 6+. Thanks