>
> My tests of Jeremy's same network on 3.1.4b did not appear to have
> memory problems, at least not in the same magnitude of
> OpenDX.  The
> amount of free memory remained right at around 62.6 MB
> (no image caching)
> and 67.1 MB total, jumping up and down a little.  With
> OpenDX, I was
> losing .5 to 1 MB at each time step.  (I ran some of my
> own animations
> with OpenDX and did not have any memory problems, about
> 25.1 MB remain
> free with jumps up and down on the order of .1 MB.   Afer
> 70+ frames the
> amount of free memory is still the same.)
>
> Running Jeremy's network on Windows 98, I get the same
> problem of using up
> all the memory, at about 1 MB per time step.  I thought
> the problem was
> coming from just one of the OpenDX module's in his network.

The OpenDx/Cygwin version Windows 98?  That is a known problem.  You
have right to yell at M$ for selling the gloriously shitty product.
Win98 itself has memory leak, which gets horrible when an
X-application (X-server) is runing because Win98 tries to be selfish
and hat to share
resources with any other server... With X-server trying to share
Display causes Win98/95 to start eating CPU resources and may once
in a while will force you to reboot the PC..... because it gets
horribly slow.

That is why i use the M$ half-decent OS, which is NT.

Suhaib

Win95/98 are good for playing games, that is what M$ likes, "play
games"

>
> The other thing to note is that I think the area
> designated for small
> items fills up first and then starts using space
> allocated for large
> items.
>
> Jeff
>
>
>
> On Thu, 4 Nov 1999, Richard Gillilan wrote:
>
> >
> >
> > I've seen what may be a symptom of the same problem and
> I've seen it for a
> > very long time, even with the commercial DX. When I run
> DX on a remote
> > machine (SGI Irix 6.5 with OpenDX in the most recent
> case) through
> > an X window on my local SGI (with setenv DISPLAY) I
> have noticed that
> > the Xsgi process on my local machine (owned by root)
> grows and grows
> > with every use of DX until memory is exceeded and very
> bad things happen
> > (X dies and sometimes the whole machine dies). At first
> I thought this was
> > related to my use of hardware rendering, but it also
> happens in software
> > mode too. The only way to clean up Xsgi's memory that I
> know of is to
> > do a console reboot using the magic key combination
> (control-shift-/-F12).
> > I don't recall if this happens when I run from the
> commercial version of DX
> > on the IBM SP2, but I'll bet it does. I'll see if I can
> do a few more tests.
> >
> > Richard
> >
> > [EMAIL PROTECTED]
> >
> >
> > ps. please respond on opendx-dev, since that is the
> only list I'm on right now.
> >
> > Thanks
> >
>
> ----------------------------------------------------------
> ------------
> Jeff Braun                        Geophysics Dept.
> mailto: [EMAIL PROTECTED]          Montana Tech
> (406) 496-4206                    1300 W. Park St.
>                                   Butte, MT 59701
>
>
>

Reply via email to