Hi An option could be to commit more often (if that's not an issue for your application of course) letting db4o to flush some state that it keeps in memory until you commit.
Best Adriano On Apr 20, 2:34 am, imran ali <[email protected]> wrote: > Hi Streets, > Thanks for reply, > > i have been following your both advice still i am having problem after > some time. > i am doing download and save data in loop, that is approx more than > 100 times > to download that much of data and in every loop i have been giving > Sleep to thread too. > it has been working for 9-10 loops after that it is giving > outOfMemory. > > so, i think it is due to db4o, because to save data i have to make > lots of objects, > there i may not be handling in proper way to clear memory. > > further any more suggestion? > > Thanks > Imran ali > > On Apr 13, 7:17 pm, Streets Of Boston <[email protected]> wrote: > > > > > > > > > My first answer would be: use less memory by chopping up the large text file > > in chunks. > > > My second answer is this: Apart from setting null values to your (temporary) > > objects, try to call System.gc() as well. It *may* improve your situation > > somewhat, since Android's (DalvikVM's) garbage collector is non-compacting. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
