Thanks for ur Suggestion.
Ooops. I tried it now still same error java.lang.outofMemoryError.
Thanks Regards
M. Karunakar
University of Hyderabad,Hyd,
9491388035.
On Thu, Mar 14, 2013 at 11:15 AM, Harish hkacho...@gmail.com wrote:
Hi
Try this code if it helps
System.setOut(new
Throwing a line of code isn't going to stop your library from
attempting to buffer a huge file...
Kris
On Thu, Mar 14, 2013 at 1:59 AM, karunakar medamoni
kannaiah.chi...@gmail.com wrote:
Thanks for ur Suggestion.
Ooops. I tried it now still same error java.lang.outofMemoryError.
Thanks
Actually even 5K can crash his app... it all depends on what he did before
the allocation.
Android has a nasty bug of claiming you dont have enough memory even if
your heap has more than enough free space if it grew close to its maximum
value previously (and dont't forget fragmentation as well,
Thanks to everyone.
Am using code which are written by the apertium people. Am just integrating
apertium program to my programs. I have increase heap size in emulator some
time i did not get any result after that i reduced heap size to middle
level at this i got same OOM error. What should i do
it depends on how much heap you defined for the emulator. if it didnt crash
with 24mb, you're pretty much safe for 99% of the devices out there (i
think even 48mb will cover most devices out there)
Otherwise, if you can't figure out a way to reduce your memory allocations,
just set the
On Thu, Mar 14, 2013 at 4:15 AM, Piren gpi...@gmail.com wrote:
Actually even 5K can crash his app... it all depends on what he did before
the allocation.
Android has a nasty bug of claiming you dont have enough memory even if your
heap has more than enough free space if it grew close to its
As far as i know it's actually a bug in android, as the allocation issue is
in the JVM, not the kernel.
Do notice that i wasn't talking about fragmentation or reaching the heap
size limit... If your heap size is 23.9MB with 100% of it free (thus,
plenty of room), i.e 0MB utilization with
Is that really the case? I haven't seen any Dalvik bug reports on
this, could you manage to point one out, or at least a post / example
backing this up..?
Kris
On Thu, Mar 14, 2013 at 10:43 AM, Piren gpi...@gmail.com wrote:
As far as i know it's actually a bug in android, as the allocation
There's quite a big discussion of this bug somewhere hidden in the bug
reports, i've come across the issue myself and found its rather easy to
replicate.
basically just write a loop that allocate a whole boat load of memory. run
it till it poops on you then limit it to do a bit less
On Thu, Mar 14, 2013 at 12:28 PM, Piren gpi...@gmail.com wrote:
There's quite a big discussion of this bug somewhere hidden in the bug
reports, i've come across the issue myself and found its rather easy to
replicate.
basically just write a loop that allocate a whole boat load of memory. run
What you're saying is true under some conditions (as i stated, i'm aware of
fragmentation)... but i think it will take quite a horrible alignment of
stars for it to fail because of the reason you stated... in my tests i
wasn't allocating huge chunks, barely 100K or so... i truly doubt every
Try bufferreader to read chunk of bytes at a time as suggested by android
.define buffer size
On 14 Mar 2013 13:46, Piren gpi...@gmail.com wrote:
Actually even 5K can crash his app... it all depends on what he did before
the allocation.
Android has a nasty bug of claiming you dont have enough
How about this test:
- Figure out the biggest allowable heap for the device
- Start a fresh app that tries to allocate one big ass object that will
expand the heap to it's maximum size within a minimal distance of it
- GC that object and make sure the Free Heap has that big ass object
space back
Can you include the full stack trace from LogCat please.
On Wednesday, March 13, 2013 11:37:16 AM UTC, karunakar medamoni wrote:
Hello
Every one. This is karunakar working on android project. Am converting
apertium based webpage to android app. When i try to run
Hello Richard
Thank u for u reply. I will be back with full stack from LogCat by
tomorrow morning.
Thanks Regards
M. Karunakar
University of Hyderabad,Hyd,
9491388035.
On Wed, Mar 13, 2013 at 6:11 PM, RichardC richard.crit...@googlemail.comwrote:
Can you include the full stack trace from
Hi Richard
Good Morning. As per your mail am attaching my android log file. Please
have look at once. I ran the same program from command line and also in
eclipse. I got the output , when i try to integrate with android am getting
this error.
Thanks Regards
M. Karunakar
University of
how big is the file you're reading..?
In general, you can't allocate that much space on Android. To combat
this you need to be able to do lazy I/O.
But ... are you trying to read in a dictionary (using apertium?). I'd
guess this is a few megabytes at least right? Having a megabyte or
two on
Hi
Try this code if it helps
System.setOut(new PrintStream(new BufferedOutputStream(new
FileOutputStream(/data/data/com.samsaadhani.sandhi1/files/output),1024)));
FileOutputStream fis = openFileOutput(input,
Context.MODE_PRIVATE);
18 matches
Mail list logo
