BufferedInputStream is throwing out-of-memory errors in Android

Question

I'm trying to use a BufferedInputStream to load an external DICOM file, but it eventually runs out of memory. When I used an InputStream, this never came up (I did this when I was loading the file through the assets folder).

I created my own producer-consumer threads to buffer the file, so I don't actually need the BufferedInputStream, but I DO need to use mark() and reset() which is not available in FileInputStream.

How should I go around this? Is there another kind of InputStream that I can use with a File which has the mark()/reset() functions? Can I empty the buffer somehow before the BufferedInputStream throws the error? Or should I find a way around using mark() instead?

Thanks for your input.

I'm using the default value (I believe that's 8024 or so). I can't create a buffer that's the size of the file because it's too big, so I have to read it in chunks. — confusedKid
– confusedKid, Commented Nov 18, 2011 at 16:43
is it possible that the chunks are too big? Have you tried smaller buffer sizes? — dMb
– dMb, Commented Nov 18, 2011 at 16:51
Ok, I tried using 4096 and 1024 buffer sizes, but both still throw oom errors. From what I can tell, it's crashing after the same number of reads. — confusedKid
– confusedKid, Commented Nov 18, 2011 at 16:57

Dave Newton · Accepted Answer · 2011-11-18 16:55:06Z

3

For mark and reset to work with buffered input the file points between the mark and reset need to remain in memory.

Workarounds depend on what you're actually trying to do; if you just need to start reading from a known location, perhaps a RandomAccessFile.

answered Nov 18, 2011 at 16:55

Dave Newton

161k27 gold badges263 silver badges310 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

BufferedInputStream is throwing out-of-memory errors in Android

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related