What happens is that it starts to eat memory until it finaly quits... On memory warning i close and open database again, I have set cache size to 50 as mentioned in some posts here, and tried putting query into statement - same result..
it just garbles mamory and app quits after 300 inserts on iphone or somewhere around 900 inserts on iPad...
Any help would be appreciated..

1 Answer
1

Wow. SQLite code is a lot of ugly compared to CoreData. But, hey, to each his own...

Use the Allocations instrument to figure out what is consuming all the memory. Off-hand and without seeing the code, is UIImage *myImage = [self getWebImage:webUrl]; potentially over-retaining the image data?

Beyond that it is hard to guess what might be going on without seeing either more of the code or more evidence.

Tried with instruments UIImage was giving me trouble, could not find why so I gave up went to get a beer, came back, put entire code into autorelease pool, deleted manual releases, added autoreleases, and memory consumption is somewhere at constant 15MB... now me one happy coder... thanks for help.. :-D
–
kviksilverMay 31 '10 at 8:21

And after all, decieded to use CoreData on my next project...
–
kviksilverMay 31 '10 at 8:22

Excellent -- sometimes, a quick step away is all it takes. For me, it is usually explaining the problem to someone else. Apparently, consuming someone else's time triggers my problem solving center.
–
bbumMay 31 '10 at 18:14