Messages in this thread | | | Date | Mon, 31 May 1999 18:31:53 -0500 | From | "Robert G. 'Doc' Savage" <> | Subject | Re: Everyone's a captain on a calm sea... |
| |
Ted,
Does your system seem to lock up? Almost no keyboard or mouse response? Does it feel like Netscape has exited abnormally and is still running as a runaway background process, consuming 99+% of your CPU cycles?
If so, this is a familiar problem with Netscape Navigator 4.0x and 4.5x. It is not Linux-specific. I know from personal experience that it also affects Solaris and 95/NT. Some think it's a bug in Java and recommend disabling that functionality. I don't think anybody knows for sure. With a little patience you can usually Telnet into an affected workstation and kill the runaway process.
Netscape has just released a 4.6 version, but it's too early to tell if it suffers from the same problem.
--Doc Savage Fairview Heights, IL
At 20:11 5/30/99 -0700, Ted Rolle wrote: >Well, it's been a well-known problem since as far back as RH 4.2. >It has persisted all this time -- I checked on #linux and others confirmed >it. > >Is there a 'back door' to get a terminal session? What about Alt-SysRq? > >My own systems have all been i486+. The lockup seems to occur at random >times when Netscape is up. There is constant disk activity during the >problem; response is slow -- 30 seconds for the cursor to move after >the mouse has moved -- sometimes. > >What information should I gather when the problem recurs? I _may_ have a >set of data that can reproduce the problem -- it is a message of my wife's >on usa.net that locked it up twice. > >I realize that this a "something's wrong, please fix it" request, but it >points to a long-standing problem: that of ending a rogue program. >Perhaps someone else can provide more information. > >On Mon, 31 May 1999, Alan Cox wrote: > >> > It seems that the OS should be able to detect a rogue application >> > and take some corrective action -- just letting me log in on a different >> > terminal to kill the offending process would be sufficient. >> >> Nod >> >> However before anyone can even guess what problems you are seeing, you need >> to provide some basic info - kernel version, architecture, general machine >> info, accurate report of the lockup
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |