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

Bug 349528

Summary:	Java was started but returned exit code=3
Product:	[Eclipse Project] Platform	Reporter:	MaximeLecourt <maxime.lecourt>
Component:	IDE	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	RESOLVED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3	CC:	casse, daniel_megert, prakash
Version:	3.6.2	Keywords:	needinfo
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description MaximeLecourt

2011-06-16 04:25:46 EDT

Hello,
I developped a plugin, which reads binary files.

I tested the plugin by launching a separate Eclipse Application using the MANIFEST.MF file, from inside Eclipse. At that time, the plugin works fine.

So I added the plugin to my dropins folder.

When launching Eclipse again, I can open the perspective I created for my plugin (so the plugin is found).
But when opening the binary file, Eclipse crashes.

I get as error (twice):
"This application has requested the runtime to terminate in an unusual way. Please contact the support team for more information"

Then, I get another message:
"java was started but returned exit code=3"

What is that error code ?

Comment 1 Dani Megert

2011-06-16 05:58:54 EDT

Is there anything in .log?
Is there a VM dump?

Comment 2 MaximeLecourt

2011-06-16 06:03:25 EDT

(In reply to comment #1)
> Is there anything in .log?
> Is there a VM dump?

Nothing in .log file.
If by VM dump you mean a hs_err????.pid file, there is none on my disks.

Comment 3 Dani Megert

2011-06-16 09:01:02 EDT

Start with -debug and check whether more stuff is logged or shown in the command console.

Also, you could remote debug the problem. There's not much we can do without either getting a dump or your plug-in.

Also, make sure you don't mix 64- and 32-bit.

Comment 4 MaximeLecourt

2011-06-16 09:36:02 EDT

Now I am getting an interesting result.

launching eclipse with -debug option, the plugin actually works fine.

As the computer is 32bit, there is no chance of mixing with 64bit system.

The whole plugin is around 70 megabites big, so it's a bit too much I think.

Comment 5 Dani Megert

2011-06-16 09:42:51 EDT

>launching eclipse with -debug option, the plugin actually works fine.
That sounds strange.

Comment 6 MaximeLecourt

2011-06-16 16:34:22 EDT

Has eclipse a different way to handle memory and heap space when in debug mode ?

Comment 7 Dani Megert

2011-06-17 01:53:16 EDT

(In reply to comment #6)
> Has eclipse a different way to handle memory and heap space when in debug mode
> ?

No, it just prints out more stuff.

Comment 8 Prakash Rangaraj

2011-06-17 10:16:21 EDT

Can you attach the code where you read the binary file?

Comment 9 Oleg Besedin

2011-06-21 10:58:06 EDT

(In reply to comment #0)
> Hello,
> I developped a plugin, which reads binary files.
> 
> I tested the plugin by launching a separate Eclipse Application using the
> MANIFEST.MF file, from inside Eclipse. At that time, the plugin works fine.
> 
> So I added the plugin to my dropins folder.
> 
> When launching Eclipse again, I can open the perspective I created for my
> plugin (so the plugin is found).
> But when opening the binary file, Eclipse crashes.
> 

Please feel free to reopen if you track down the problem to something in the Eclipse code base.

Comment 10 MaximeLecourt

2011-07-26 03:47:25 EDT

Apparently it's not an Eclipse bug. We believe we have a structure that is allocated but not freed.

Comment 11 Hugues Cassé

2011-07-28 13:43:28 EDT

(In reply to comment #10)
> Apparently it's not an Eclipse bug. We believe we have a structure that is
> allocated but not freed.

When launched with -debug mode activated, the program is currently working ?