On Mon, 18 May 1998, Hilarion wrote:
>
> On 18-May-98 Brad Alexander playfully chanted:
> | I'm running E-BETA-0.13.3, Imlib-1.3, ImageMagick-4.0.5, libjpeg-6a,
> | libpng-0.96, etc on a RedHat 5.0 system with XFree86. P-100 with 64MB
> | RAM/64MB swap, Diamond Stealth 64 (PCI) with 2MB DRAM.
> |
> | I have noticed that when running E in 16bit color, when using heavy
> | grafx-type apps like Gimp and Netscape, the machine will lock up. I have
> | done the same as root (running WindowMaker), with more Gimp pictures open
> | and Netscape and did not have a problem. I have been playing with
> | customizing xdm, and the default bit depth was at 8 bits. When logged in
> | to my user account in 8 bits, I got one generic Eterm open and it locked
> | again...These were hard freezes, I was not even able to three-finger
> | salute. I have noticed an increase in the frequency of these lockups
> | since upgrading RedHat and the new libs. With 4.2 and all the old libs, I
> | would get a random lockup after about 2 weeks. Now it is every couple of
> | days, but seemingly only when running E.
>
> Just asking--have you tried to see whether a memory leak (with that combo...)
> is making you run out of swap without you noticing? Real far shot, but that's
> all I've got.
Actually, I thought it was a problem with xlock (under 4.2), but I quit
running that and just went back to xset s. Under 5.0, no I didn't have top
or anything like that running. I should run xosview or something and make
it sticky, I guess. I'll try that.
> Second question: you can't use the keyboard, but can you move your mouse?
> Could just be X locking up, and taking the keyboard with it. 'Sbeen known to
> happen. If it takes the pointing device too, it'll look like a NMI-freeze too
> so if it reaches that point, it's indistinguishable.
Its everything. Mouse, keyboard, video, the works.
> Try the process of elimination--disable the java or don't use Netscape and play
> the odds--see how long you can go without a freeze. Netscape's been known to
> have memory leaks.
Several times it happened with xlock. I know some of the modules have
severe memory leaks, so I limited it to galaxy, which seemed to behave
itself most of the time. Although I never tried xlock is in blank
mode...Now, though, it doesn't matter, since its happening more often.
Thanks,
--Brad
-
To unsubscribe from this list send mail to: [EMAIL PROTECTED]
with the message contents: unsubscribe e-develop
