i have an app with a scrollable view with 15 images and an index. when i open the app on my ipad the available memory is 132. just pulling up the index drops it to 72. flipping through a few pages drops it down to 2 and then it crashes.
am i doing something wrong? i'll post the code if necessary but as stated its just a very simple scrollable view with a scroll view index. Help would be greatly greatly appreciated.
Seems similar to this bug: http://developer.appcelerator.com/question/46061/serious-memory-leak
I also have the same issue, every scroll is decreasing the Free memory available… Unless this is fixed soon, this makes the scrollableView component useless.
If anyone from the dev. team is reading this, what's the best way to tackle this please?
the crashing i was talking about above was on an ipad. i just realized that the app runs perfectly on the iphone4. while the available memory decreases significantly it never crashes on the iphone using the exact same resources. can anybody tell me why? thanks
This could be due to an iPhone4 having twice the RAM of an iPad.
- iPhone4 has 512M RAM
- iPad has 256M RAM
Apple may need to launch a new iPad with 512M to get fast app switching and multitasking working smoothly in iOS 4.2
does anyone from appcelerator care enough to respond? im about to transition back to objective C if i cannot solve this. thanks
I agree, memory management is very disappointing in Titanium. You cannot imagine how it' hard to tell client 'sorry, we cannot finish your project because of SDK failure'. You are investing millions so HIRE SOMEONE TO FIX IT!! This is critical bug.
I have blogged my answer, have a look
Same here, I am big disappointed with the Titanium background worker, memory management, threading, packaging etc. Its really hard to tell client 'sorry, we are taking time because of SDK failure'. Titanium is having critical bugs.
This issue should be fixed in the 1.7 release. I have an early release of it an it appears to fix this problem.