SiteAdmin wrote:I would try adding your books back one at a time until you find the one that is causing the problem.
It turns out the problem is not with my books. I have done some methodical testing this morning. (I'm a software engineer, so I understand about debugging and possible failure modes).
After uninstalling and reinstalling, and turning icon view off, the program will open while it is in guest mode. I could close and re-open. I could terminate (up-flick) and re-open. As soon as it had synced with my iGigBook account, the next restart caused it to crash.
So in Content Manager, I made all the books non-Active (that was tedious, having to go Edit->untick->Save for each one - could we have a single list of checkboxes and a Save button?).
I then uninstalled and reinstalled. Ok so far. I logged iGigBook into my account. The first time I did this, the program crashed when I tapped on "My Scores", so I uninstalled and reinstalled again. Again guest mode was fine (no indexes shown in Book List). This time when I logged iGigBook in, it was fine. I could navigate around, close/open, terminate/open, all ok.
I did find testing was slowed down rather by the aggressing rate-limiting on the server for synchronisations. I had to wait 6 minutes at one point.
I then made a single index active: ** NEED HELP?
After waiting a while and then syncing, I saw the ** NEED HELP line in the Book List. However, terminating and restarting the program caused the crashing to start again. So note that this is with NONE of my PDFs installed, and ONLY the NEED HELP? index set to active in Content Manager.
I read the updated post at the head of this thread, so I tried terminating and restarting a LOT of times, and it made no difference.
So, next, I de-activated NEED HELP and activated the Bach Cello Suites, as the PDF comes with iGigBook. I then uninstalled and reinstalled. Guest mode ok. Logged in and synced - Bach Cello Suites now shown in the Book List and I could navigate via the titles to the music. I could close (not terminate) the app and open it again. However, when I then terminated the app and re-opened it, it crashed again on opening, and then continues to do so.
- Why does the program try to create icons even when the "show as icons" option is OFF? Surely it would be more sensible not to do so until they are needed!
- If it were a low memory issue, (a) why does it still occur when no other apps are running and the program is just starting up? and (b) couldn't the low-memory return (e.g. from malloc()) be checked for and sanely reported?
- Don't you think it is likely to be something more fundamental than just memory?
- Could you make 2.61 available again via the App Store while this issue is investigated?
Pity it's not an open source project - then I and others could help suggest fixes!