www.saintmarys.edu/~pbays/ST/St.htm
It will be clear from the alerts and the appearance of the page what is and what is not complete at this point.
PROBLEM: I am a Mac user. (That is NOT the problem!!) In safari I am running into a memory leak, I think. If I run the page many times (hitting the "new problem" button), I can eventually get cpu usage up to the max and Safari hangs. Now this takes 30-40 iterations. But, I have seen students sit at the computer for hours doing tutorials like this, so 30-40 problems will not be at all unusual. This raises some questions for me.
1. Is the fault of the applet? I don't think so since it seems to run on Windows browsers without the problem -- though I would like confirmation of that.
2. Is it the fault of my code? A good possibility. If so, is there a way to "clear memory" without removing the applet after each problem?
3. Is it the fault of Safari? I have no control over that :(.
If the applet is loaded for the first problem, I was under the impression it is not reloaded for each successive one; it knows it is there; it is simply refreshed with new data. Is that correct? If not, is there a way to make it so? That is, I do not want to be loading up memory with multiple unused copies of the applet.
Phil
J. Philip Bays Professor of Chemistry Science Hall 158 Saint Mary's College Notre Dame IN 46556 (574) 284-4663
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Jmol-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-users
