"Linux.org Albania SysAdm (Kledi)" wrote:
> 
> Hi,
> 
> I have been running X for much time, but during the last month, I've
> encountered some problems... X shuts down with no reasons very often...
> sometimes I get this message:
> 
> waiting for X server to shut down xterm:  fatal IO error 32 (Broken pipe)
> or KillClient on X server ":0.0"
> 
> or nothing, that seems like a normal X shutdown.
> I have noticed, that always the shutdowns happen when netscape is running,
> and this makes me think it could cause a crash. (I've got Netscape Comm.
> 4.05, that came with RH51, but now I'm downloading Comm. 4.5).
> 
> About a month ago I upgraded my VRAM to 4M. Could this happen because of a
> bad chip? Anyway it should report something I guess if it's a VRAM
> problem.
> 
> thanks
> Kledi

Bad VRAM will cause a display error (the output to the screen will be
wrong).  I can't think of any way to make bad VRAM affect the operation
of a program such that it would crash.  If you read bad memory, it would
be (probably) all-black (zeroes) or all-white (one's).  If you write to
memory that isn't present, the data gets lost.  That's just about it.

You are probably running out of swap space.  Now that you have more RAM,
you probably have increased the resolution.  That gives you larger root
windows.  You probably have a pretty picture in the root window; you may
have several if you have multiple desktops.  Each new desktop root
window image will take extra memory.  

You may have increased the color depth, which means that each
application is using double, triple or even quadruple the dynamically
allocated memory for images.

Cheers, JeremyC.
-- 
Jeremy Chatfield, Xi Graphics  mailto:[EMAIL PROTECTED]  tel:+44(0)1234.710030 
 Commercial X Products: Servers, CDE, contracts and custom development
    http://www.xig.com ftp://ftp.xig.com/ mailto:[EMAIL PROTECTED]
     tel:+1.303.298.7478  fax:+1.303.298.1406  mailto:[EMAIL PROTECTED]

S/MIME Cryptographic Signature

  • X Problems Linux.org Albania SysAdm (Kledi)
    • Jeremy Chatfield

Reply via email to