How to clear ram working on List<byte> and byte array?

Question

0.00/5 (No votes)

See more:

I am working on mp3 streaming. I used Mark Heath's NAudio.dll for this project. But streamed mp3 frames must be decompressed to listen. I m using List and byte array to storage data. So that ram using is over 200 mb on every mp3 playing. But main problem is my code throw OutOfMemoryException exception after 3 or 4 song played. I tried "=null and Clear()" method but it seems it doesnt work.How can I fix this problem. Thanks in advance.

Posted 24-Apr-15 6:48am

Amt-Coder

Updated 24-Apr-15 13:13pm

v3

Add a Solution

Comments

Richard MacCutchan 24-Apr-15 13:08pm

Stack overflow is usually caused by overuse of local variables instead of heap storage.

Sascha Lefèvre 24-Apr-15 21:16pm

Please add the relevant code to your question.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2015-04-24T08:06:00

Solution 1

Stack overflow has nothing to do with the size of Lists, or arrays of any description - in C# these are always Reference types, and as such are stored on the Heap, not the stack.

So look at your code: the most likely reason for a Stack Overflow Exception is that you have some inadvertent recursion eating your stack rather than anything directly to do with the structures you are storing data in.

Posted 24-Apr-15 8:06am

OriginalGriff

Comments

Amt-Coder 24-Apr-15 19:12pm

sorry I wrote it wrong. It should be OutOfMemoryException. I have edited

OriginalGriff 25-Apr-15 5:03am

You gotta be accurate about these things, my friend! :laugh:

That's a whole new world of pain...
Start by looking at your .NET framework version: prior to V4.5 the Large Object Heap wasn't compacted, so it's possible that a change to the framework version will slow or prevent the problem (if it's the heap becoming fragmented so it can't allocate a new block of the requested size). It's unlikely, but it's generally simple to change and could be diagnostic.

After that, you need to know exactly what is going on - and that's complicated. Start with a memory profiler - VS 2012 had one built in:
http://blogs.msdn.com/b/dotnet/archive/2013/04/04/net-memory-allocation-profiling-with-visual-studio-2012.aspx
And see if that tells you what objects you are allocating.

But...I'd guess it's that you are allocating a lot more memory than you think, and not destroying the references, or that you are trying to allocate far, far too big a chunk of memory (no single .NET object can be larger than 2GB, and an array of bytes is a single object for example). Start with the profiler and see if you can work out what is being allocated for a single track.

Without your code? I can't do much from here!