Re: Errant ld-linux.so.2
Patrick Wiseman wrote: > Every now and then, I have an apparently memory-leaking ld-linux.so.2 > process running. When I kill it, nothing else seems adversely > affected. Is there some way I can identify what's spawned it? > > Patrick > > I have seen this happen several times in the last few weeks. If it happened before that too, I think I didn't notice! This happens when I open an pdf document with Adobe Reader 8 inside Konqueror (file browsing). Killing it doesn't hurt anything else but reduces the CPU usage to the normal few %. /KS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Errant ld-linux.so.2
On Tue, Mar 25, 2008 at 5:22 AM, Joost Witteveen <[EMAIL PROTECTED]> wrote: > > On 25/03/2008, Patrick Wiseman <[EMAIL PROTECTED]> wrote: > > Every now and then, I have an apparently memory-leaking ld-linux.so.2 > > process running. When I kill it, nothing else seems adversely > > affected. Is there some way I can identify what's spawned it? > > Normally you would be able to see what process spawned what using > ps axf > > (f: ASCII-art process hierarchy (forest)) > But I suppose in your case you may not see much interesting output. > In that case, I'd write a short shell script that does ps ax>file > continually, to try and see when the process starts to appear. Thanks - I've been using Linux for years and never knew you could do that (see the forest, that is)! I think I'll probably wait until there's an instance running and then discover what spawned it. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Errant ld-linux.so.2
On 25/03/2008, Patrick Wiseman <[EMAIL PROTECTED]> wrote: > Every now and then, I have an apparently memory-leaking ld-linux.so.2 > process running. When I kill it, nothing else seems adversely > affected. Is there some way I can identify what's spawned it? Normally you would be able to see what process spawned what using ps axf (f: ASCII-art process hierarchy (forest)) But I suppose in your case you may not see much interesting output. In that case, I'd write a short shell script that does ps ax>file continually, to try and see when the process starts to appear. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Errant ld-linux.so.2
Every now and then, I have an apparently memory-leaking ld-linux.so.2 process running. When I kill it, nothing else seems adversely affected. Is there some way I can identify what's spawned it? Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
