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

Bug 322942

Summary:	[launcher] eclipse/java process always has an exit code of -1073741819 when Permeo SOCKS client is installed
Product:	[Eclipse Project] Equinox	Reporter:	John Cortell <john.cortell>
Component:	Launcher	Assignee:	Project Inbox <equinox.launcher-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	remy.suen
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description John Cortell

2010-08-17 14:34:54 EDT

I installed the Permeo SOCKS client the other day, and suddenly my headless builds started failing. It turns out that after installing Permeo, the eclipse/java process always ends up loading a new dll--one of Permeo's. Specifically, s5spi.dll. This is true even when the SOCKS service is disabled.  

With s5spi.dll loaded, eclipse seems to run fine. However, on exit the result code is non-zero (specifically, -1073741819)

To reproduce:
1. Install Permeo Premium Agent 5.1 (see below). You'll be told to reboot. Don't bother. The problem is reproducible at this point.
2. Open a Windows command prompt and cd to where Eclipse is installed (I've tried Helios and Ganymede; same behavior)
3. Run 'eclipsec.exe'
4. Eclipse come up fine. Shut it down
5. At the command line, type 'echo %ERRORLEVEL%. You'll get -1073741819. Note that there is nothing new in the Eclipse error log.
6. Rename C:\Program Files\Permeo\Premium Agent\s5spi.dll to anything (e.g., s5spi.dll.disable). 
7. Repeat steps 3-5. You'll see that the error level is now 0.

So, apparently the permeo dll causes something to go wrong on shutdown, but what exactly is a mystery. Since permeo is not a free tool, I understand this will be a difficult issue to take on.  I'm opening this bug just to have the issue on record. I'll be happy to provide/try things on behalf of whomever wants to get to the bottom of the problem. Also feel free to just close this bug. Again, at a minimum, I just wanted to publicly record the problem.

Comment 1 Eclipse Genie

2019-03-20 10:46:21 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 2 Lars Vogel

2019-10-08 10:47:54 EDT

This bug was marked as stalebug a while ago. Marking as wontfix.

If this report is still relevant for the current release, please
reopen and remove the stalebug whiteboard tag.