Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

Fix for scrollable view memory issues? - Will Pay

i have tried everything i know to free up memory on my app including using the removeView method to remove all but 2 views at a time and it doesnt help at all.

appcelerator quoted me $350/hr for 'architecture support' which i think is steep. anyone have a fix that they would share for less?

— asked November 20th 2010 by sean oreilly
  • crash
  • memory
  • scrollable

5 Answers

  • This is well known Ti bug and not "limits of the platform". Scrollable views are one of the most basic UI elements of iPhone so this issue should be top priority for Ti dev team anyway.

    After month of fighting with Ti bugs and "limits of the platform" (like documented features which actually don't work as advertised and non-answered error tickets on lighthouse) I am also starting to look at Obj-C.

    — answered November 26th 2010 by Deniss Fedotovs
  • Thank u. The issue is I've asked here and have seen numerous others with the same unresolved issue. I imagine that it's not that hard a fix and would hate for appcrlerator's team to tell me it took 3 hrs and bill me $1000+ for an app that I probably won't make a great deal of money on.

    So I tried to incentivize the community to help.

    — answered November 20th 2010 by sean oreilly
    • Sean

      I have no knowledge of Appcelerator's contracts, or whether they have minimum terms but, looking at the plans, if you took the "professional" plan for 3 months, it would only cost $600.

      This forum is for discussing and sharing Titanium-related technical problems so, if you won't specify yours, I don't know how else we can help.

      — commented November 20th 2010 by Paul Dowsett
    • sorry if the problem wasnt explained clearly.

      its a simple scrollable view using full res images (1024 x 768). it runs out of memory. i have attempted to release the views using a few methods including a simple for loop …

      (list is the array of views)
      for (var t=0; t<list.length; t++){

      but nothing seems to free up any memory.

      — commented November 20th 2010 by sean oreilly
    • oh and regarding the professional plan. the email i received from appcelerator specified that the plan did not include issue resolution and hence the $350/hr figure. if you know otherwise please advise. thanks

      — commented November 20th 2010 by sean oreilly
  • Sean

    You haven't posted any working code yet. If you want to do so, and image assets are required to demonstrate the issue, it would probably be best if you zip the project (or a stripped down version of it) and upload it somewhere.

    — answered November 26th 2010 by Paul Dowsett
  • I have blogged my answer, have a look


    — answered February 3rd 2011 by Shakil Bharucha
    1 Comment
    • honestly, this makes things only worse..there are flashes when you scroll..thank you anyways

      — commented March 28th 2011 by Alberto Marcone
  • Sean

    This Q&A forum is intended for people to describe requirements that are possible within the limits of the platform, so that everyone can discuss possible solutions in a public space so that others may benefit in future.

    You are welcome, for free, to post some stripped-down, working code (so that it can be dropped into a project and it runs without modification), and someone in the community, I am sure, will try to help you.

    The advantage, I imagine, of employing the development team's skills directly, via one of the support plans, is that you will almost certainly get a workable solution, even if it involves reprioritization of existing tickets or enhancements to the codebase.

    I'd recommend at least trying the first suggestion. If you are pressed for time or unwilling to share some example code, then the latter is your most reliable option.

    — answered November 20th 2010 by Paul Dowsett
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.