Crashes After Launch when attempting to exit rendered image (iPod Touch)
I didn't post this in the thread about crashing at launch, because it's not quite that.
As you guys probably know, when you first fire up Molecule, it defaults to the render screen, where it renders whichever molecule you last selected for rendering. When I first downloaded the program, I had no problems just tapping the little "i" button on the render page to go to the list of available molecules.
The problems started arising after I downloaded new molecule structures from the Protein Database. The new molecules would render with no problem, and, satisfied, I would exit the app. The next time I entered the app, the render screen popped up as it usually does, with the rendered image of the last new molecule I downloaded. Cool. I tapped the "i" button to go back to the list, and the message "Scanning Files" with the swirling progress circle comes up. After 10-20 seconds of this, instead of taking me to the list of available molecules, the program crashes back to the home screen. I tried it a couple more times with the same results. Being a PC user at heart, I also tried rebooting my iPod Touch, but that didn't solve the problem either. The only thing that does work is deleting the application and re-downloading it, but then the problem comes back anytime I add new structures.
This isn't a huge problem for me since I'm not a chemist/biologist by profession and mostly just have Molecule on my iPod to remind me of my days as a chemistry major before becoming a lawyer, but it is a problem nonetheless that hopefully can be resolved. Thanks!
I forget which specific molecules I had the first two times this occurred, but I just replicated it on my iPod with PDB code 1o1k (Hemoglobin Alpha Chain).
I just tried 1o1k on the latest version I have here (1.0.1 with some minor tweaks) and it ran fine. The problem might be solved by the update, or it might be that I'm testing it on an iPhone (original, not 3G). The number of atoms is far less than others I've tested against, but I did notice that the journal publication fields were missing, so I'll see if that causes any memory problems that might lead to a crash.
I've heard from other developers that they are seeing some mystery crashes that only hit certain users and seem to be cleared with a system restore, indicating a problem with the 2.0 firmware. Hopefully, this is not one of those.
I just tried out the 1.0.1 update and still have the same crash; it's probably one of those mysterious 2.0 firmware issues of which you speak. Since my use of Molecules is mostly for my own entertainment, it's not compelling enough right now for me to wipe my iPod clean and start anew. Thanks for the help, though.
Oh well. I'll keep looking to see if I can track down anything on my side of things that could be causing this. Thanks for testing again and sorry about the problems you're having.
I've been having the same issues as kf6tac above. I'm using Molecules on an original iPhone running version 2.0 of the iPhone software (build 5A347 that was pushed via iTunes). I've tried adding " CRYSTAL STRUCTURE OF THE HELICASE DOMAIN OF THE GENE4 PROTEIN OF BACTERIOPHAGE T7" (code 1cr0), the hemoglobin molecule mentioned above, and "COMPLEX OF E.COLI DNA TOPOISOMERASE I WITH 3'-5'-ADENOSINE DIPHOSPHATE" (code 1cy0). I too was hoping that the 1.0.1 update would fix the problem, but alas that's not the case. I'm not using Molecules quite enough to put myself through a system restore, but if that indeed turns out to be the only cure, I might be willing.
This problem aside, congratulations and thank you for a nice app!
Hi
First of all I want to congratulate you for doing this app. I'm from Spain and I'm studying biology, and I have to tell that it's really cool and useful for me!! Thanksss :)
But I have the same problem, the one that happens after downloading one molecule from PDB. I've tried with several ones and it allways happens :(
Hope that you can find a way to fix it soon :)
Thanks again
Danny
What specific molecules (PDB codes) did you grab? I'd like to see if I can repeat this to figure out what's wrong.
There was a slight problem in the way that the 1.0 version handled the initial scanning, so whenever the 1.0.1 update gets pushed out to everyone that might solve it. I'd like to test and see if it does, though.
Deleting the application works to clear the error because the Gzipped PDB files are downloaded to the application's sandboxed /Documents directory. When you delete the application, the /Documents directory gets wiped as well, along with any application preferences and settings. Re-downloading it starts you with a fresh /Documents directory and blank preferences.
As I said elsewhere in the forums, I'm going to try to cut down on the Scanning... and Rendering... times by caching a lot of that to disk.