Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'had trouble' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
had trouble
Authored by: SOX on Jan 26, '04 12:18:44PM

When I get to the 3-D movable image for the first update from spirit my 512MB computer just hangs at the point of loading 60% of the images. Well it doesn't hang exactly: I can rotatte the partial image. It just never completes the load. Is this a memory issue? any body else see this? (I am running 10.3.2. on an 800Mhz iMac. I tried downloading it a second time but got the same results.



[ Reply to This | # ]
had trouble
Authored by: Reddog on Jan 26, '04 02:28:03PM

I don't know if your problem is lack of memory, but the Maestro program DOES like lots & lots of memory. I have a DP 1.42 G4 with 1.5 gig of ram and Maestro uses every bit of it that it can and then pages out another gig to virtual memory after I've been playing with it a while..

Go to the View menu and play with Imaging Performance memory cache. Maybe that will help you.

Pat



[ Reply to This | # ]
had trouble
Authored by: LFransson on Jan 26, '04 02:31:44PM

I don't think it's strictly a memory issue. I have 1.25 GB RAM, and I'm not getting past 60% either.

---
Larry Fransson
Seattle, WA



[ Reply to This | # ]
had trouble -- limited real RAM
Authored by: Krazy on Jan 27, '04 12:16:04AM

I too have had problems with 512 Mb of RAM. I've yet to download the spirit data updates, but even using the test data, I only get to around 98% of the data loading. What is confusing is the progress bar gets stuck there. First time I saw this I thought the program had hung. Also I've noticed lots of 'WARNING' messages output to the console....

Having experimented recently moving my virtual memory to a rather small but separate partition, (1GIG = 2 x real RAM), I was not surprised at all to see disk full warnings (for the swap partition) -- at which point the sensible solution was to kill the app. It seems to be a real memory hog! I guess the developers have loads of memory to burn so have no reason to make it work in a small memory footprint.

I suggest that people complain if they are having problems via Maestro's Forums: http://mars.telascience.org/forums



[ Reply to This | # ]
had trouble
Authored by: sjha on Jan 27, '04 11:41:00AM

I have exactly the same problem - 1GHz G4 iMac with 512MB memory running OSX 10.3.2

---
Steve Ashcroft



[ Reply to This | # ]