🚀 go-pugleaf

I had some similar problem where an NXImage was allocated in a particular  
zone and the the zone was destroyed (long long later). The image was NOT  
NAMED any way, and not referenced explicitly in my application.

Then, in some random part of the program (often when quitting) the program  
would crash with a Bus Error. I had to investigate long (yes I should have  
RTFM) to find that

1) Always void all references to an NXImage before freeing, appkit objects  
have a long memory of what image they used, be sure you REALLY tell them  
not to use that image.
2) Always explicitly free a NXImage which is in a Zone you might destroy.
3) And then you are allowed to gracefully destroy the zone.

PS: I am REALLY HAPPY to see some NeXT dev support people posting some  
REALLY interesting articles. Please continue, this may help all of us.
-- 
----
Benoit Grange - PARIS - FRANCE

Mail to : ben@fizz.fdn.org (SMALL NeXTMails accepted, < 10kb)