At 10:44 PM -0800 2/10/02, Ken Norris (dialup) wrote: >I just tried to access the Image Library. The window took a long time to >open. When it finally did, it showed a block of icon-type images, and some >animated barber poles, one of which had a blank space where it looks like >one of them should have been, the circular arrows in motion, and a scroll >bar. NOTHING WORKED. The cursor was still working, but that's all. I >couldn't access anything at all. My machine had soft-crashed again; I had to >force a keyboard restart. > >I really don't like this behavior. Rev has done this 3 times already, twice >with the docs (Dictionary, Encyclopedia), and now with the image library. >It's got me spooked. What's next? > >It also caused display problems with other applications, such as Outlook >Express, (left big blank spaces on the display), and the screen looks like >the desktop is (sometimes slowly) being rebuilt every time I close Rev, >which, BTW, usually takes about 3 times as long as Photoshop 6. > >Any suggestions?
(I'm assuming you're on a Mac running < OS X) This absolutely sounds like a "running out of memory" issue. I tend to notice it when Finder icons in the background start taking about a second each to redraw. Revolution takes a certain amount of memory to run -- 20MB. It then dynamically grabs whatever extra it needs when you do things like open the image library or the documentation. Giving Rev more memory to start with generally won't help, and can hurt. Revolution won't use the extra memory you give it in place of the dynamic allocation it grabs for. So assigning it more simply means that less free memory is available for it to grab. Revolution will grab until there is no more available. Several other applications use the same dynamic memory technique. Notable among these is the Finder itself. I think most Microsoft apps too. If Revolution grabs all the free memory, other applications that use the same dynamic allocation method will inevitably want a little more themselves at some point, and none will be available. Hence the really slow redraws. There are at least three things you can do to help: First, make sure you haven't assigned too much memory to Revolution. Try it with the default and see if you have problems. Second, get more memory -- it's cheap. Third, watch how many aspects of the development environment you open during a single session. I wrote the RTFer stack, which goes through all the documentation in order to save it out. Opening all the different pieces of the documentation pops the memory use up to about 60MB without breaking a sweat. Finally, note that while the applications you create with Revolution also use the dynamic memory allocation scheme, they are likely to require far less memory, and you are in control of how much. Things like loading all your images into the application rather than referencing them push up your memory use. Finally finally, you can change Rev's memory allocation method. Check the Troubleshooting section of the help, under Why is Revolution Taking More Memory Than Its Allocation. regards, geoff _______________________________________________ improve-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/improve-revolution
