> In response to Suhaib's post: > > 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 running 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. > Actually, I was able to create the problem under NT as > well. The problem is > not with CPU resources, but memory usage. It seems like > OpenDx isn't releasing > memory somewhere, so eventually it fills up its memory > limit (-memory 200) and > won't release any of it. Nothing effects the system, > except the dx network > won't run until you disconnect/reconnect the dxexec to > force the release of > memory. > > Thanks for the responses! Let's keep at it so we can > figure out what's going > on here...
Get a CPU resources monitor and try to watch resources consuption and Windows 98/95 not releasing resources to X applications. You will notice this problem with any X app, not just OpenDX. I have tested this over and over again during developemnt of several X clients. it is Win98/95. The M$ engnieers do not know how write an OS which could be stable and share resources properly. > > Jeremy Zoss > Southwest Research Institute > (210)522-3089 > [EMAIL PROTECTED] >
