|
President of the Imperial Galactic Government
Joined: Aug 2004
Posts: 7,950 Likes: 19 |
Have you looked at the diagnostic and usage logs? They are situated in the settings/about screen and I am sure that Meridian would find the one most recent to the time of problem useful to them. You will need to look at the logs (and content) to see whether the log references Core Control.
When iOS runs low on memory resources, iOS7 send certain applications a memory low message. The app should then respond to this message and free up memory hogging resources, like deleting UI features such as buttons/images etc - anything that the app is holding in memory but doesn't actually need at that moment in time but can recreate on demand.
My theory is that Core Control us freeing up memory by deleting buttons etc. but not recreating them before they are needed again. It is known that core control is quite memory hungry and can be jettisoned from memory entirely by iOS which people may interpret as an app crash but is just iOS being heavy handed with its crude memory management.
Sound like this could be some half way house to being jettisoned. With the help of the logs, Meridian can then see if they need to test the app in simulated low memory conditions.
I'm not trying to defend Meridian, but if there was a rush to get the app out by a deadline, handling low memory conditions would probably be low on the list of priorities of getting things to work and in the euphoria of a new release and zero budget remaining, the culture these days is often, it ill do.
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).
|