#3759 jedit stopps when I type (windows 8)

open
nobody
5
2013-10-07
2012-11-28
Chris
No

I use Windows 8 Pro, 32-Bit-Betriebssystem, x64-basierter Prozessor,

Download and Installation of jEdit 5.0.0 was successful
start jedit, loading documents, including plugins (lilypond) is successful
clicking into the text of a file (test.ly) is successful
The moment try to type something the GUI stops working
To kill jedit, I have to kill java (jedit process is not enough)
I have Java(TM) 6 Update 21
An Update zu Java 6 Update 37 showed no improvement

Who can help me?

Regards,
Chris

Discussion

  • Thomas Meyer
    Thomas Meyer
    2012-12-02

    Please follow these steps:

    1.) install a JDK and start this program: "C:\Program Files\Java\jdk1.7.0_09\bin\jvisualvm.exe" (change the path accordingly)
    2.) in VisualVM: attach to the running jEdit process by dobule clicking the process
    3.) choose tab "Thread" and click the "thread dump" button
    4.) attach the thread dump here.

     
  • Thomas Meyer
    Thomas Meyer
    2012-12-03

    Hi,

    thanks for the report. This seems to be some kind of deadlock:

    1.) AWT event queue thread is waiting on the WriteLock of the Buffer:

    \"AWT-EventQueue-0\" prio=6 tid=0x045bdc00 nid=0x18ac waiting on condition
    [0x05b8e000]

    java.lang.Thread.State: WAITING (parking)
    at sun.misc.Unsafe.park(Native Method)
    - parking to wait for <0x290197d8> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
    at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
    at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
    at java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:945)
    at org.gjt.sp.jedit.buffer.JEditBuffer.writeLock(JEditBuffer.java:285)
    at org.gjt.sp.jedit.buffer.JEditBuffer.insert(JEditBuffer.java:719)
    at org.gjt.sp.jedit.buffer.JEditBuffer.insert(JEditBuffer.java:684)
    at org.gjt.sp.jedit.textarea.TextArea.insert(TextArea.java:5460)
    at org.gjt.sp.jedit.textarea.TextArea.userInput(TextArea.java:3412)
    at org.gjt.sp.jedit.textarea.JEditTextArea.userInput(JEditTextArea.java:294)
    at org.gjt.sp.jedit.gui.InputHandler.userInput(InputHandler.java:425)
    at org.gjt.sp.jedit.gui.DefaultInputHandler.handleKey(DefaultInputHandler.java:167)
    at org.gjt.sp.jedit.input.AbstractInputHandler.processKeyEventKeyStrokeHandling(AbstractInputHandler.java:405)
    at org.gjt.sp.jedit.gui.InputHandler.processKeyEvent(InputHandler.java:129)
    at org.gjt.sp.jedit.textarea.TextArea.processKeyEvent(TextArea.java:4724)

    Your thread dump sadly doesn't reveal the owner of the lock "0x290197d8". This is the important thread, if this thread is block, the GUI will be blocked.

    2.) The sidekick plugin is waiting for the mediatracker lock, but that seems to be unrelated.
    \"SwingWorker-pool-1-thread-1\" daemon prio=6 tid=0x068a1400 nid=0x1a48 in Object.wait
    () [0x0713f000]

    java.lang.Thread.State: WAITING (on object monitor)

    at java.lang.Object.wait(Native Method)
    - waiting on <0x28f17b00> (a java.awt.MediaTracker)
    at java.awt.MediaTracker.waitForID(MediaTracker.java:667)
    - locked <0x28f17b00> (a java.awt.MediaTracker)
    at javax.swing.ImageIcon.loadImage(ImageIcon.java:302)
    - locked <0x28f17b00> (a java.awt.MediaTracker)
    at javax.swing.ImageIcon.<init>(ImageIcon.java:192)
    at javax.swing.ImageIcon.<init>(ImageIcon.java:205)
    at lilytool.parser.AssignAsset.<clinit>(AssignAsset.java:19)
    at lilytool.parser.LilySideKickParser$Block.addToNode(LilySideKickParser.java:619)
    at lilytool.parser.LilySideKickParser.simpleParse(LilySideKickParser.java:478)
    at lilytool.parser.LilySideKickParser.parse(LilySideKickParser.java:112)
    at sidekick.SideKick$ParseRequestWorker.doInBackground(SideKick.java:550)
    at sidekick.SideKick$ParseRequestWorker.doInBackground(SideKick.java:526)
    at javax.swing.SwingWorker$1.call(SwingWorker.java:296)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at javax.swing.SwingWorker.run(SwingWorker.java:335)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)

    You may try to disable the sidekick plugin and see if this solves your problem?

     
  • Thomas Meyer
    Thomas Meyer
    2012-12-04

    Chris responded:
    "Your Analysis ist great. The deactivation of the SideKick-Plugin helps to work with the
    Editor. Unforunately the plugin is necessary to work with the Lilypond Plugin. I used jEdit
    mainly for work with Lilypond. The Workaround: deactivate SideKick (and Lilypond) - work
    in the Editor - activate Lilypond and sidekick - compile the file - deactivate .... would work,
    but ist not nice. The Moment I type something without deactivation, lilypond freezes.

    Do you have any idea how to repair sidekick, get the media-traker to answer or use
    lilypond without it?"

     
  • Thomas Meyer
    Thomas Meyer
    2012-12-07

    Hi Chris,

    would you please provide the version numbers of the plugins you are using? You can find the version numbers in "Plugins->Plugin Manager".

    Can you also please attach the test.ly file in this bug report?

    I'll try to reproduce the bug.

     
  • Alan Ezust
    Alan Ezust
    2013-10-07

    • labels: 102668 --> Windows Specific