Ian Bridges wrote: > > re my previous post and some of the replies... > > > > > The Mac OS allocates a fixed amount of memory to each application. If an > > application requires additional memory, it can make a system call to > > request temporary memory for itself, over and above the application's > > assigned allocation. This temporary memory appears in the Finder's "About > > This Computer" window, and in other utilities that display memory use, as > > part of the application's assigned allocation. > > The only app I had seen do this in the past that I had noticed was the > Finder & I thought that was a special case. > > Installed RAM is a non issue with 300+ megs on board, so I can allocate > plenty to Rev if needs be. I do find it curious tho, that no other app I use > does this as far as I can tell - all of them give low memory or out of > memory warnings when stressed (which is why I always allocate at least 10Mb > more to the preferred size), so it looks like they don't use this mechanism, > which does make me wonder why - is there a stability issue with doing this? > > All of my Rev stability issues seem to be Type 2 errors which I believe are > memory related, so could this be part of the cause? I'll try Rev with a > 100Mb allocation and see how I go...
I don't think increasing the ram is gonna do it. Can you reproduce the crushes? > > Do standalones created with Rev allocate more RAM like this too? > > If you think this is going a bit OT reply to me off list. > > Ian B Andu
