Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!fido.wpd.sgi.com!moose.asd.sgi.com!jwag
From: jwag@moose.asd.sgi.com (Chris Wagner)
Newsgroups: comp.sys.sgi
Subject: Re: Shared Memory Problems
Message-ID: <1991Jun5.155551.13195@fido.wpd.sgi.com>
Date: 5 Jun 91 15:55:51 GMT
References: <9106041435.AA00794@sct60a.sunyct.edu>
Sender: news@fido.wpd.sgi.com (Usenet News Admin)
Organization: Silicon Graphics, Research & Development
Lines: 43

In article <9106041435.AA00794@sct60a.sunyct.edu>, sweetmr@SCT60A.SUNYCT.EDU (michael sweet) writes:
|> 
|> We are developing an application which uses large amounts of shared memory
|> (about 2 Mb in the current configuration) to track different types of datafiles.
|> During integration with other pieces of the project on another machine, we
|> have run into an error/bug that gives the error:
|> 
|>  "Could not find window slot in shared memory"
|> 
|> This is from the NeWS server, and appears on the console whenever the integrator
|> tries to open a new window.  She has/is placing a call to the SGI hotline, but
|> I figured you people here might be of more help...  The specifics of the
|> shared-memory segment we're using and the the machine are:
|> 
|>  Model:    4D/20, 16Mb physical memory, 100Mb swap
|>            IRIX 3.3.1
|> 
|>  Shared Memory Segment ~2Mb, using a key value of 6809, and mapped to address
|>  0x02000000.
|> 
|> I believe she is running Workspace as well when this happens.  Any guesses?
|> 
|> 
|> 
|>  -Mike Sweet
|> 
|> ------------------------------------------------------------------------------
|> "The only        TASC                      (315) 724-1100 (voice)
|>  truth is that   555 French Road           (315) 724-2031 (fax)
|>  there are no    New Hartford, NY  13413   Internet: sweetmr@sct60a.sunyct.edu
|>  truths, only beliefs."                    Delphi:   DODGECOLT
|> ------------------------------------------------------------------------------

-- 
There were some virtual memory problems in 3.3.1 for large programs
using lots of segments (like linking with a bunch of shared libraries)
that could cause erroroneous memory references - I have never seen
this occur on a PI, but its possible - I would strongly recommend
that you upgrade to 3.3.2 (I know, I'm sounding like the hotline)
and see if the problem disappears.

----
Chris Wagner (jwag@sgi.com)