#666 error when spliting editor for the same file


Version: Juno Service Release 2
Build id: 20130225-0426
Epic 0.6.49

Steps to Reproduce:
open a perl file to edit
window \ new editor

"failed to create the part's controls"
at org.epic.perleditor.popupmenus.ExplainErrorsRulerAction.getMarkersForLine(ExplainErrorsRulerAction.java:86)
at org.epic.perleditor.popupmenus.ExplainErrorsRulerAction.update(ExplainErrorsRulerAction.java:65)
... (see attachment)

1 Attachments


  • Jan Ploski

    Jan Ploski - 2013-08-08

    Tested with freshly installed Eclipse Juno "Classic" 4.2.2 (build M20130204-1200) and EPIC 0.6.53 under Linux and can't reproduce this problem. Most likely something else in your environment is causing it.

  • Jeff

    Jeff - 2013-08-08

    Here is some more information. It seems related to the state when I have compile errors in my current file but they are not in my current view area. See the attached image.
    In the attached case, I had global variable references which perl could not resolve.

    If my file does not have any compile errors then I am able to split the view.

  • Jan Ploski

    Jan Ploski - 2013-08-08

    I still can't reproduce it - "New Editor" works whether or not errors are in the file and whether or not they are "below the fold" or immediately visible after opening the first editor. Maybe you can post a smaller file which demonstrates the problem?

  • Jeff

    Jeff - 2013-08-08

    It's not file specific, but has something to do with the state of the editor. I am guessing that if you load up the attached file and open a new editor it will work.

    Sometimes I was able to get an error if I started at line 22 and added about 300 empty lines (by hitting the return key), saving the file and then trying to open a new editor. The annoying things was that my editor is currently in a state where if I open a new editor on the attached file, every time I get the error. I am fine if you want to close this as not reproducible.

  • Jan Ploski

    Jan Ploski - 2013-08-09

    As you suspected, openning new editor on the attached file works ok for me, even after adding blank lines. So it may be caused by the devil after all. ;-) Another possibility is that it might have something to do with stale breakpoints. Do you see any breakpoints in the Breakpoints view that you could remove from the file and which no longer match a line number?

    • Jeff

      Jeff - 2013-08-09

      My gut instinct tells me that it has something to do with the markers on the on the right which you can mouse over and get more information. The top of the stack trace refers to "ExplainErrorsRulerAction.getMarkersForLine". The error is a null pointer exception, so my guess is that somehow eclipse/epic is loosing track of the markers.

      I am just happy that the new editor for the same file feature is not completely broken and that I can use it. :)

  • Oliver Trosien

    Oliver Trosien - 2016-05-15
    • status: open --> closed-invalid
  • Oliver Trosien

    Oliver Trosien - 2016-05-15

    Tried on 0.7.0 without issues (it's called Editor > Clone in Eclipse Mars)


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks