+1 for better memory management needed overall. I experience multiple DragonSoul crashes daily on an iPhone 5S (yeah, it's overdue for an upgrade, yet no other apps crash on it..) and my trusty Galaxy Note 3.
On the Note, I'm able to view DS crash reports most of the time, which ALWAYS indicate an out-of-memory condition. Usually, it's trying to allocate a contiguous block larger than what's currently available due to memory fragmentation, even though there's plenty of free memory overall. Interestingly, the same crash occurs even after restarting the phone, with no other apps running in the background. Unfortunately, I'm never able to see exactly how much memory DragonSoul is consuming when the crash occurs, and all of that memory is freed up when it restarts.
I actually just triggered a crash right now in guild war with my Android Studio debugger attached. There were 2 separate out-of-memory errors in a row during my attack:
02-07 22:39:13.887 2259-27685/? E/art: Throwing OutOfMemoryError "Failed to allocate a 772 byte allocation with 16777120 free bytes and 373MB until OOM; failed due to fragmentation (required continguous free 65536 bytes for a new buffer where largest contiguous free 61440 bytes)"
02-07 22:39:13.887 2259-27685/? E/RPGAssetManager: Setting MISSING_ADDITIONAL flag for: Assets/ETC/XHDPI/world/units/hero_dragon_slayer.skel_world/units/hero_dragon_slayer.atlas
02-07 22:39:15.237 2259-6591/? E/art: Throwing OutOfMemoryError "Failed to allocate a 1014 byte allocation with 16776896 free bytes and 373MB until OOM; failed due to fragmentation (required continguous free 65536 bytes for a new buffer where largest contiguous free 61440 bytes)"
It appears that Android crash reports are automatically submitted to GREE via the New Relic monitoring service (commonly used for mobile apps), so they should be able to look for patterns. Something similar might also be in place for the iOS app, as well. If so, I can't imagine why this isn't a higher priority for them to fix.