[antlr-interest] Issue with antlrworks 1.3.1 and JDK 1.6 update 17?

Kaleb Pederson kaleb.pederson at gmail.com
Wed Jan 6 12:51:03 PST 2010


On Wed, Jan 6, 2010 at 3:33 AM, Michael Richter <ttmrichter at gmail.com> wrote:
> I did a recent round of upgrading software on my machines (real and virtual)
> and somewhere in the process I've got ANTLRworks in unusable shape.  (I
> tried reporting this through the antlr.org web site but it doesn't seem to
> have taken.)
>
> On *every* machine I have access to (both real and virtual, running Windows
> XP or Linux) I get the following pretty nasty behaviour:
[...snip...]

> The behaviour on Linux is less acceptable.  The new project wizard pops up
> but the text input focus is on ANTLRworks' editor window and CANNOT be put
> into the wizard at all on any spot.  I have to cancel the wizard to get to
> the main window (which then works as expected).

My AW preferences were set load the last file on each invocation,
which seems to work fine.  I changed my preferences to go to use the
wizard after which I started seeing some problems.

I started up AW, the 'New Document' dialog showed up.  I hit Cancel.
The UI disappeared but the application kept running.  I did a 'kill
-QUIT $AW_PID' and received the attached dump (I know Ter's been
playing with the mailing list filters and things, so we'll see if it
actually goes through).  The dump shows that AW is awaiting feedback,
but with no GUI present, it will never receive it.  This happens with
both 1.3 and 1.3.1, although the dump is for the 1.3.1.

> This also happens if I go
> File -> New from the main window: I simply cannot get text input into any
> field of the new project wizard.

I can replicate this behavior on Linux.  Does the following workaround
work for you:

a) Click OK (using an empty grammar name)
b) Dismiss the dialog that says you used an empty grammar name
c) Left click in the grammar name input field to give it focus
d) Now type in the wizard as usual?

A related note, I've seen this behavior on many different Java
applications, so I'm not sure if it's Java related, or if it's just an
error that is easy to make when writing the application using Java.

> Any advice for debugging this further?

I also tried removing the AW preferences and disabling focus-stealing
prevention in my window manager, but neither of those helped either.

Looks like a couple of real bugs to me.

--
Kaleb Pederson

Blog - http://kalebpederson.com
Twitter - http://twitter.com/kalebpederson
-------------- next part --------------
2010-01-06 12:22:44
Full thread dump Java HotSpot(TM) 64-Bit Server VM (14.3-b01 mixed mode):

"Timer-1" prio=10 tid=0x0000000040e40800 nid=0x69a1 in Object.wait() [0x00007f06eb31b000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)                             
        at java.lang.Object.wait(Native Method)                                          
        - waiting on <0x00007f0721c6d7c8> (a java.util.TaskQueue)                        
        at java.util.TimerThread.mainLoop(Timer.java:509)                                
        - locked <0x00007f0721c6d7c8> (a java.util.TaskQueue)                            
        at java.util.TimerThread.run(Timer.java:462)                                     

"DestroyJavaVM" prio=10 tid=0x00007f06ec3ec000 nid=0x698d waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE                                                                

"Timer-0" daemon prio=10 tid=0x00007f06ec8f7800 nid=0x699f in Object.wait() [0x00007f06eb41c000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)                                    
        at java.lang.Object.wait(Native Method)                                                 
        - waiting on <0x00007f072148e720> (a java.util.TaskQueue)                               
        at java.util.TimerThread.mainLoop(Timer.java:509)                                       
        - locked <0x00007f072148e720> (a java.util.TaskQueue)                                   
        at java.util.TimerThread.run(Timer.java:462)                                            

"AWT-XAWT" daemon prio=10 tid=0x00007f06ec2d2000 nid=0x699b runnable [0x00007f06f0288000]
   java.lang.Thread.State: RUNNABLE
        at sun.awt.X11.XToolkit.waitForEvents(Native Method)
        at sun.awt.X11.XToolkit.run(XToolkit.java:548)
        at sun.awt.X11.XToolkit.run(XToolkit.java:523)
        at java.lang.Thread.run(Thread.java:619)

"Java2D Disposer" daemon prio=10 tid=0x0000000040b04800 nid=0x699a in Object.wait() [0x00007f06f0389000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00007f072226ddf8> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
        - locked <0x00007f072226ddf8> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
        at sun.java2d.Disposer.run(Disposer.java:125)
        at java.lang.Thread.run(Thread.java:619)

"Low Memory Detector" daemon prio=10 tid=0x0000000040b1c000 nid=0x6998 runnable [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"CompilerThread1" daemon prio=10 tid=0x0000000040b19000 nid=0x6997 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"CompilerThread0" daemon prio=10 tid=0x0000000040b16000 nid=0x6996 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" daemon prio=10 tid=0x0000000040b14000 nid=0x6995 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Finalizer" daemon prio=10 tid=0x0000000040af6800 nid=0x6994 in Object.wait() [0x00007f06f1fde000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00007f072226e3f0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
        - locked <0x00007f072226e3f0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=10 tid=0x0000000040aef000 nid=0x6993 in Object.wait() [0x00007f06f20df000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00007f072226e540> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:485)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
        - locked <0x00007f072226e540> (a java.lang.ref.Reference$Lock)

"VM Thread" prio=10 tid=0x0000000040ae8800 nid=0x6992 runnable

"GC task thread#0 (ParallelGC)" prio=10 tid=0x00000000409cf800 nid=0x698e runnable

"GC task thread#1 (ParallelGC)" prio=10 tid=0x00000000409d1800 nid=0x698f runnable

"GC task thread#2 (ParallelGC)" prio=10 tid=0x00000000409d3000 nid=0x6990 runnable

"GC task thread#3 (ParallelGC)" prio=10 tid=0x00000000409d5000 nid=0x6991 runnable

"VM Periodic Task Thread" prio=10 tid=0x0000000040b1e800 nid=0x6999 waiting on condition

JNI global references: 1281

Heap
 PSYoungGen      total 18496K, used 13856K [0x00007f07212e0000, 0x00007f0722780000, 0x00007f0735ce0000)
  eden space 15872K, 70% used [0x00007f07212e0000,0x00007f0721ddf770,0x00007f0722260000)
  from space 2624K, 98% used [0x00007f0722260000,0x00007f07224e88a0,0x00007f07224f0000)
  to   space 2624K, 0% used [0x00007f07224f0000,0x00007f07224f0000,0x00007f0722780000)
 PSOldGen        total 42240K, used 488K [0x00007f06f7ee0000, 0x00007f06fa820000, 0x00007f07212e0000)
  object space 42240K, 1% used [0x00007f06f7ee0000,0x00007f06f7f5a000,0x00007f06fa820000)
 PSPermGen       total 21248K, used 17747K [0x00007f06f2ae0000, 0x00007f06f3fa0000, 0x00007f06f7ee0000)
  object space 21248K, 83% used [0x00007f06f2ae0000,0x00007f06f3c34f10,0x00007f06f3fa0000)


More information about the antlr-interest mailing list