Community
Participate
Working Groups
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 ?
Is there anything in .log? Is there a VM dump?
(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.
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.
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.
>launching eclipse with -debug option, the plugin actually works fine. That sounds strange.
Has eclipse a different way to handle memory and heap space when in debug mode ?
(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.
Can you attach the code where you read the binary file?
(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.
Apparently it's not an Eclipse bug. We believe we have a structure that is allocated but not freed.
(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 ?
