Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333962

Summary:

Network operations hang if pxgconf does not return the value in time

Product:

[Eclipse Project] Platform

Reporter:

Robert Munteanu <robert.munteanu>

Component:

Team

Assignee:

Platform Team Inbox <platform-team-inbox>

Status:

RESOLVED DUPLICATE

QA Contact:

Severity:

normal

Priority:

CC:

jamesblackburn+eclipse

Version:

3.6.1

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
stack traces for eclipse when restarting	none
backtrace for pxgconf	none
Partial ps output, showing eclipse and its child processes	none

Description Robert Munteanu

2011-01-11 07:06:47 EST

Build Identifier: 

I have seen on some occasions that Eclipse 'hangs' during network operations. Trying to restart Eclipse has no effect , as the network-related jobs are all hung.

By taking a thread dump I have noticed that:

- one thread holds the lock for org.eclipse.core.net.ProxyProvider ;
- other threads are waiting to lock the ProxyProvider;
- the thread holding the said lock is waiting for a process to exit

Running ps I have noticed that Eclipse has a child process spawned: /usr/lib/libproxy/pxgconf , which is by itself hung.

Reproducible: Sometimes

Steps to Reproduce:
1.Perform network operations in Eclipse

Comment 1 Robert Munteanu

2011-01-11 07:08:29 EST

Build id: 20100917-0705
gtk2-2.20.1-2.13.x86_64

Comment 2 Robert Munteanu

2011-01-11 07:10:15 EST

Created attachment 186478 [details]
stack traces for eclipse when restarting

Comment 3 Robert Munteanu

2011-01-11 07:11:04 EST

Created attachment 186479 [details]
backtrace for pxgconf

Comment 4 Robert Munteanu

2011-01-11 07:12:32 EST

Created attachment 186480 [details]
Partial ps output, showing eclipse and its child processes

Comment 5 Robert Munteanu

2011-01-11 07:13:08 EST

Even though the faut is clearly in an external component and not Eclipse, I think a guard should be but in place for such misbehaviour on pxgconf's behalf.

Comment 6 James Blackburn

2011-01-11 07:23:26 EST

It's actually running '/bin/sh -c 'env'' and your env process has become defunct...

This should all be fixed by bug 332728 where we'll use Java API for this by default.

*** This bug has been marked as a duplicate of bug 332728 ***