[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (room) side effects
- To: info-mcl@ministry.cambridge.apple.com
- Subject: Re: (room) side effects
- From: lind@ils.nwu.edu (Jeff Lind)
- Date: Sun, 12 Jun 1994 18:19:19 -0500
- Followup-to: comp.lang.lisp.mcl
- Newsgroups: comp.lang.lisp.mcl
- Organization: Institute for the Learning Sciences
- References: <2tag0j$p3t@anaxagoras.ils.nwu.edu>
In article <2tag0j$p3t@anaxagoras.ils.nwu.edu>,
allender@aristotle.ils.nwu.edu (Allender ) wrote:
> We are trying to uncover the nature of a weird side-effect. We
> have a large image that was built using MCL 2.0.1, Wood and Oodles
> of Utils. The image was created on a Quadra 800. The image
> runs well enough on the 800 and on my FX. It often runs just
> fine on our Quadra 950. Recently, the image (which has not
> been altered) started acting "cranky" on the Quadra 950.
>
> If I type (room) before starting up my multimedia program, it runs
> fine. If I don't, I get gworld allocation errors.
I've seen things like this before, too, Laura. Probably your mac heap
starts out small, and you ask for a bunch of memory during your startup and
(for some reason) it can't grow the mac heap to accomodate you. I usualy
set the mac heap to be pretty big as one of my first actions. Start up your
stuff and see how big it is. Then do a (set-mac-heap-size x) to make it
nearly that big when you start. That function is defined in qt-objects,
btw.
--Jeff