Memory Leak Help

Question

I wasn't keeping an eye on the profiler and the taskmanager for my Game's memory. Now, when I decided to check, I certainly do have a memory leak. The profiler shows(also the task manager) my memory is increasing by 1MB everytime I run the game. So, I tried everything, including my code check, couldn't figure it out. finally decided to make a backup of the whole game folder then tried deleting all the assets one by one starting with the game scripts until I ended up with only just the first scene. Still the Same leak(1mb increase each time I run my game). I don't know what to do, Anyone out there can solve my problem?

I cannot attach the game, because I don't want to give out all my codes or assets.

Answer 1

Answer by roamcel · Aug 17, 2011 at 05:29 AM

I have read a similar issue from another user who was intentionally allocating and deallocating and observing the memory behavior after their deallocation.

http://answers.unity3d.com/questions/153050/memory-management-and-list.html

Since he reported the same amount of memory leak after each execution, I suggested that he quit the game and checked if the memory was freed or not, but he performed a slightly different check.

So, have you checked that unity frees the memory or not after you quit it? I haven't been able to reproduce the issue.

As a side note, I read that instantiated textures aren't destroyed automatically. Does your scene perform any particular texture operations?

Add comment · Show 12 · Share

peter8989 · Aug 17, 2011 at 06:14 AM 0

Share

it does free the memory, the memory always starts at the same value in my case. I even restarted the computer lol. same result!

peter8989 · Aug 17, 2011 at 06:15 AM 0

Share

but its kinda weird, those two people said they were having the same "1MB" problem too, seems like a UnityGC bug perhaps?

roamcel · Aug 17, 2011 at 08:08 AM 0

Share

I actually believe this might be a bug now. I suggest you pack up your test project and report a unity bug. This doesn't seem to be automatically reproducible.

CHPedersen · Aug 19, 2011 at 11:32 AM 1

Share

It is. :) Warwick is totally right, here. Remember that a program's allocation of any kind of resource is at the mercy of the OS. Whenever you write "int i = 0", your runtime system runs like a well-trained schoolboy to Windows and says, "Can I have 32 bits, pretty pleeeeease?". That's why unmanaged code written in C and C++ sometimes throws pesky AccessViolationExceptions if you attempt to write to unallocated memory - this is actually the OS telling your program to back off and mind its own business, because it tried to write into areas of memory reserved by the OS, and it refused your program access. Because the OS is the authority when it comes to GRANTING your program resources, it is also responsible for cleaning up AFTER your program has finished execution. Leaks made by your program manifest while the program runs. Not afterwards.

Waz · Aug 19, 2011 at 12:47 PM 1

Share

In your List question, you appeared to believe that allocating a load of memory and then freeing it should result in the memory usage shown in the Task Manager being unchanged. That might seem intuitively obvious, but it is not true. Programs allocate large chunks from the operating system, then manage handling little 4-byte ints etc. themselves, merely marking something as free (but not necessarily handing it back to the OS). When you think you've just done 100,000 allocations and deallocations, what makes you certain Unity hasn't allocated 4 bytes amongst that for something else (meaning the entire block cannot be reallocated, even if it happened to somehow all be in a new fresh block)?

I am not saying that there is no leak, I'm saying that all the evidence I've heard makes invalid assumptions about memory allocation.

If you go back one step further, you'll see that the "1MB texture taking 2MB!!" was also a result of invalid assumptions about memory.

Certainly even a real leak of 1MB that only happens in the Editor once every Play is rather irrelevant (once people have learned that the OS discards all allocations upon process termination). If Unity stays running long enough to hit Play 1000 times without freezing or crashing, it probably shows some EasterEgg for all we know...

Show more comments

Answer 2

Answer by peter8989 · Aug 21, 2011 at 09:40 PM

The analyst replied after he ran the same empty scene, and confirmed that there is a 1MB memory leak. He assured that he will reply after talking with the devs.

Add comment · Show 1 · Share

__maja__ · Nov 22, 2015 at 04:09 PM 0

Share

2011 ... The analyst takes its time.

Memory Leak Help

2 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions