Menu

#178 Eclipse hangs with latest version

v1.2.0
closed-fixed
None
7
2007-11-26
2007-10-22
No

Hi i just upgraded from nice working 1.1 to 1.2 and suddenly there are Errors in the problem view. That cannot be cause i disabled the texlipse builder.

another problem i get very often is that eclipse just hangs, the window isn't repainted and i have to kill it.

dunno if i catched the exception that is responsible for that:

java.lang.StringIndexOutOfBoundsException: String index out of range: 42
at java.lang.String.charAt(String.java:558)
at net.sourceforge.texlipse.editor.HardLineWrap.doWrapB(HardLineWrap.java:301)
at net.sourceforge.texlipse.editor.TexAutoIndentStrategy.customizeDocumentCommand(TexAutoIndentStrategy.java:135)
at org.eclipse.jface.text.TextViewer.customizeDocumentCommand(TextViewer.java:3544)
at org.eclipse.jface.text.TextViewer.handleVerifyEvent(TextViewer.java:3573)
at org.eclipse.jface.text.source.projection.ProjectionViewer.handleVerifyEvent(ProjectionViewer.java:1250)
at org.eclipse.jface.text.TextViewer$TextVerifyListener.verifyText(TextViewer.java:404)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)

Discussion

  • Boris von Loesch

    • priority: 5 --> 7
     
  • Boris von Loesch

    Logged In: YES
    user_id=343531
    Originator: NO

    You describe two bugs here.
    There could be errors in the problem view which are caused by the parser, e.g. missing braces. Please give an example of the error.
    For the second bug, please give short instructions how to reproduce it.

     
  • Stefan Lischke

    Stefan Lischke - 2007-10-22

    Logged In: YES
    user_id=646968
    Originator: YES

    Errors in problem view:
    i switched back to 1.1 and parser errors are not displayed in problem view and in the editor (no red cross marks)
    But the outline still works in 1.1, so there must be a major change between 1.1 and 1.2 handling parser errors.

    I can not reproduce the hang problem, cause i switched back to 1.1 and cannot switch back, cause i need it in productive environment. sorry for that

     
  • Nobody/Anonymous

    Logged In: NO

    I also experience that Eclipse hangs. It happens every time I hit Enter when the cursor is at the end of the line
    \begin{block}{}. The stack trace from the log:

    !ENTRY org.eclipse.ui 4 0 2007-11-12 12:07:17.125
    !MESSAGE Unhandled event loop exception
    !STACK 0
    java.lang.NullPointerException
    at net.sourceforge.texlipse.editor.TexlipseAnnotationUpdater.testSelection(TexlipseAnnotationUpdater.java:302)
    at net.sourceforge.texlipse.editor.TexlipseAnnotationUpdater.update(TexlipseAnnotationUpdater.java:104)
    at net.sourceforge.texlipse.editor.TexlipseAnnotationUpdater.selectionChanged(TexlipseAnnotationUpdater.java:85)
    at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2546)
    at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2498)
    at org.eclipse.jface.text.TextViewer$5.run(TextViewer.java:2477)
    at org.eclipse.swt.widgets.Display.runTimer(Display.java:3745)
    at org.eclipse.swt.widgets.Display.messageProc(Display.java:2967)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2265)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3291)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
    at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

     
  • Boris von Loesch

    • assigned_to: nobody --> borisvl
     
  • Boris von Loesch

    Logged In: YES
    user_id=343531
    Originator: NO

    The bug is fixed and the fix was checked into cvs. Remark, that
    it could last one day until the anonymous cvs is also updated.

     
  • Boris von Loesch

    • status: open --> open-fixed
     
  • Boris von Loesch

    • status: open-fixed --> closed-fixed
     
  • Boris von Loesch

    Logged In: YES
    user_id=343531
    Originator: NO

    Fixed in version 1.2.1

     

Log in to post a comment.