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

Bug 350996

Summary: [registry] Eclipse Crashing:java.io.UTFDataFormatException: malformed input around byte 7 as first error in log
Product: [Eclipse Project] Equinox Reporter: deepak.subu
Component: ComponentsAssignee: equinox.components-inbox <equinox.components-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: daniel_megert, deepak.subu, remy.suen
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
The log file which forms when eclipse is first started none

Description deepak.subu CLA 2011-07-02 15:04:21 EDT 
Build Identifier: I20100608-0911

I was working on eclipse a day before this crash and it was working fine. 
I first clicked on the eclipse shortcut on my windows platform and it crashes everytime without exception.
I see a prompt asking me to check to the log in the configuration directory. For each time I run eclipse a new log is generated.



Reproducible: Always

Steps to Reproduce:
1.Just start eclipse shortcut
2.
3.
Comment 1 deepak.subu CLA 2011-07-02 15:07:06 EDT 
Created attachment 199004 [details]
The log file which forms when eclipse is first started
Comment 2 deepak.subu CLA 2011-07-02 15:09:30 EDT 
(In reply to comment #0)
> Build Identifier: I20100608-0911
> 
> I was working on eclipse a day before this crash and it was working fine. 
> I first clicked on the eclipse shortcut on my windows platform and it crashes
> everytime without exception.
> I see a prompt asking me to check to the log in the configuration directory.
> For each time I run eclipse a new log is generated.
> 
> 
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1.Just start eclipse shortcut
> 2.
> 3.

That doesnt sound very sensible. 
1. Start eclipse
Comment 3 Dani Megert CLA 2011-07-05 02:54:05 EDT 
- Did you maybe change the VM or the encoding? Or even copy the workspace from another machine?

- Does it work if you use a new workspace?

See also bug 245407.
Comment 4 Oleg Besedin CLA 2011-07-07 14:11:43 EDT 
Indeed, this looks like another instance of the bug 245407.

As a workaround, "-clean" runtime argument will clear the cache.

Could you look through the bug 245407 comment 1 and see if anything in that list applies?

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