Bug 405851 - IncompatibleClassChangeErrors after restarting Eclipse
IncompatibleClassChangeErrors after restarting Eclipse
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Andrew Overholt
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-30 08:32 EST by Mary Ellen Foster
Modified: 2009-01-09 00:22 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 00:22:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Eclipse log excerpt showing the sequence of errors (ignore the mylyn spam) (82.98 KB, text/plain)
2007-11-30 08:32 EST, Mary Ellen Foster
no flags Details

  None (edit)
Description Mary Ellen Foster 2007-11-30 08:32:36 EST
Description of problem:
I still sometimes have PermGen crashes from Eclipse, even after increasing the
maximum size to 512M. (I normally have about 8 JDT projects, 2 CDT ones, and one
PyDev one open at the same time -- developing a distributed modular system -- so
that may contribute). Sometimes, after Eclipse has crashed and restarted, I
can't open any JDT editors; I get an error that says:

    Error opening the editor.

I'll attach the full backtrace from .metadata/.log for one such sequence,
beginning from the sequence of PermGen errors that crashed Eclipse and ending
with the IncompatibleClassChangeError. There's some spam from mylyn that's
probably not interesting -- it always seems to happen on start-up -- but the
NullPointerExceptions from ant aren't always there and may also be interesting.

Version-Release number of selected component (if applicable):

How reproducible:
Sometimes (sorry ...)

Steps to Reproduce:
1. Run Eclipse until it crashes
2. Restart Eclipse
3. Try to open a JDT editor
Actual results:

Expected results:
Edit some Java

Additional info:
Usually, restarting Eclipse a second time clears the error
Comment 1 Mary Ellen Foster 2007-11-30 08:32:36 EST
Created attachment 273781 [details]
Eclipse log excerpt showing the sequence of errors (ignore the mylyn spam)
Comment 2 Andrew Overholt 2007-11-30 09:33:53 EST
I sometimes get this error, too :( .
Comment 3 Bug Zapper 2008-11-26 03:45:54 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Andrew Overholt 2008-11-26 10:15:54 EST
I haven't seen this in Fedora 9 or 10 FWIW.
Comment 5 Bug Zapper 2009-01-09 00:22:59 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.