🚀 go-pugleaf

In article <Bz5rC9.1A9@rice.edu> steve@ion.rice.edu (Steve Ludtke) writes:
> 
> For the last few days I've been working on a molecule display app using  
> renderman. It's now working perfectly, with one exception. Whenever I try to  
> draw a large molecule (300-400 spheres), renderman chokes. I get a message on  
> the console about renderman losing it's connection to the window server or  
> something. After digging around the filesystem for a while, I located the place  
> where the renderman daemon writes ITS errors, and discovered a variety of  
> messages all boiling down to "out of memory", including some that explain why  
> it can't connect to the window server (memory problems again). Thinking back, I  
> remember similar problems when I tried to put too many spheres in when  
> debugging Plot3D.   Is there any way to increase the amount of memory the  
> renderman daemon has available to it???  NeXT's complete lack of documentation  
> doesn't help the situation at all!    Any advice at all would be greatly  
> appreciated!

This is a bug in the QRman server- A real pain.  You can't really play around  
with large data sets because all of a sudden, QRman can't handle it anymore and  
messes up the window server, and woops... there goes the window server!! Really  
annoying, and kinda makes you wonder how robust and useful QRman really is. I  
haven't been able to do anything 'real' on it yet!! 

BTW, Dave Springer @ NeXT is 'aware of this problem,' and has been trying to  
track it down for the last month or so. My bet is we're not gonna see any real  
fix before 3.1.

-----------------------------------------------------
Patrick Heynen 		Program of Computer Graphics
			Cornell University

patrick@yabba.graphics.cornell.edu