[SOLVED] Insane 0.6 GB memory allocation on iOS app - reasons?

[photonic]

Hi there,
I am experiencing above total memory allocation although the profiler shows me only,

26 MB texture memory (using NGUI atlases and some compressed textures)
17 draw calls
180 MB audio memory (I need wav-files streaming from disk)

Can it be that multiple ArrayLists and HashTables (referencing gameobjects) are the reason for this?

I am kind of devastated and would appreciate any help.
Thanks a lot!

[jeanfabre]

Hi,

 you need to profile it to know exactly where the memory leak is.

 Do you load scenes in and out? that could be the problem.

Bye,

 Jean

[Marsh]

Is this immediate or does the memory slowly climb. If the latter it is most likely a memory leak.

[photonic]

the memory allocation is up to 0.57 right from the start and creeps its way further during runtime.

I turned off all FSM suspecting Arraylists and Hashtable generation. .. didn't help

 

[Marsh]

Disable one thing at a time until you find it, fun stuff eh.

[photonic]

[UPDATE]
Ok, now it's obvious that using wav-files and "streaming from disc" allocates this big chunk of memory ...
What can I do if I need the original wav-length in order to jump to specific sample-positions?

thanks a lot!

 

[Marsh]

I always get annoyed when people ask questions instead of answering, but with that said.

Why do you need them to be wav files? Wouldnt something a little smaller do? Are these always the same files or are you getting them off the users device? If they are always the same files just read the lengths in a post process script and save it to a file or something.

[jeanfabre]

Hi,

 I have IOS projects with lots of videos and it's fine, I think your problem is the following:

 are you referencing the file directly? if you do, then it has to be loaded in memory. The key is to NOT point to it directly and simply use a string as the path and let Unity find it on its own.

You'll need to load these resources at runtime, ONLY when needed.


 Bye,

 Jean

[photonic]

Hi Jean,

thanks for your reply.

I used a String Compare to enter two different State Machines depending on the chosen language. There I set an audioClip-variable referencing the appropriate audio files directly. Then I switched the audioClip of my single audioSource as needed, using the mentioned audioClip-variables.

Funny workaround was: I created an empty gameObject with its own audioSource for every audioFile I would need (=4 + 1 soundtrack) and this astonishingly reduced the allocated memory by 250MB ... crazy ;-)

Got my app out to the App Store just in time :-)
... will tweak that subject further ...

Thanks a lot for your suggestions

[jeanfabre]

Hi,

 Very godd. Thanks for the update.

bye,

 Jean