Home/ Questions/Q 6552605
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T12:28:47+00:00

We have a web service iPhone app which fetches short texts (no graphics) in

  • 0

We have a web service iPhone app which fetches short texts (no graphics) in increment of 10 records – user can load more records by pressing ‘load more’ button. (akin to ‘load 25 more’ in default ‘App Store’ App)

Currently, NSXMLParser is used to parse the XML, the records are stored then in NSMutableArray, and new records (from ‘load more’) are appended to the array.

Now, we are experiencing two problems, which we believe are related to our current method of storing the records into the RAM. These are:

  1. In low memory conditions, when we switch back to the App from app switcher, and then press ‘back’ button from the detail view, App either crashes or reloads the table view!
  2. After having just 400 records loaded the app crashes!

To combat these issues, will, just storing the records into SQLite (or Core Data) instead of an array, do it? Or we need to do something more/different?

Please guide!

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    resolved it… after reading @Steven’s comment… I got convinced that it was not memory issue… so, I digged further, & found the issue.

    Actually, I have a deselectRowAtIndexPath method in tableview. And in low memory environment, iPhone releases the records stored in memory… so, in that situation, deselectRowAtIndexPath was pointing to nothing, which was causing the crash… modified & resolved it now!

    Thanks!

    • 0