Window+TextArea+(c)twm crashes JVM on keypress

Name: moC74494 Date: 05/15/98


Using the twm or ctwm window manager on Solaris
2.5.1, I'm able to reliable crash the JVM (both
jdk1.2beta3 and jdk1.1.5 (both native and green)
when I type on the Window shown when running the
following code:
---
    public static void main(String[] args) {
Frame f = new java.awt.Frame();
Window popUp = new Window(f);
popUp.setLayout(new GridLayout(1,0));
popUp.setSize(100,50);
TextArea cont = new TextArea();
//Canvas cont = new Canvas();
//cont.setSize(100,50);
popUp.add(cont);
popUp.pack();
popUp.setLocation(50,50);
popUp.setVisible(true);
    }
---

Crashlog as follows:
---
SIGSEGV 11* segmentation violation
    si_signo [11]: SIGSEGV 11* segmentation violation
    si_errno [0]: Error 0
    si_code [1]: SEGV_MAPERR [addr: 0x0]

        stackbase=EF243D94, stackpointer=EF242D6C

Full thread dump:
    "AWT-Motif" (TID:0xed704bb8, sys_thread_t:0xfc6e0, state:R, thread_t: t@8, sp:0xee793230 pc:0xef70bdf0 threadID:0xee793e00, stack_base:0xee793d94, stack_size:0x22000) prio=5
        java.awt.EventQueue.postEvent(EventQueue.java:64)
        sun.awt.motif.MToolkit.postEvent(MToolkit.java:296)
        sun.awt.motif.MComponentPeer.postEvent(MComponentPeer.java:223)
        java.lang.Thread.run(Thread.java)
    "AWT-Input" (TID:0xed704bd8, sys_thread_t:0xfc9a0, state:CW, thread_t: t@7, sp:0xee7c3698 pc:0xef70aa38 threadID:0xee7c3e00, stack_base:0xee7c3d94, stack_size:0x22000) prio=5
    "AWT-EventQueue-0" (TID:0xed704bf0, sys_thread_t:0xf1d40, state:R, thread_t: t@6, sp:0xef242c40 pc:0xef70bdf0 threadID:0xef243e00, stack_base:0xef243d94, stack_size:0x22000) prio=5 *current thread*
        java.awt.Component.dispatchEventImpl(Component.java:1817)
        java.awt.Component.dispatchEvent(Component.java:1704)
        java.awt.EventDispatchThread.run(EventDispatchThread.java:63)
    "SIGQUIT handler" (TID:0xed7002b0, sys_thread_t:0x84760, state:R, thread_t: t@5, sp:0x0 pc:0x0 threadID:0xef3c3e00, stack_base:0xef3c3d94, stack_size:0x22000) prio=0
    "Finalizer thread" (TID:0xed700088, sys_thread_t:0x846d0, state:CW, thread_t: t@4, sp:0xef3f3b10 pc:0xef70aa38 threadID:0xef3f3e00, stack_base:0xef3f3d94, stack_size:0x22000) prio=1
    "main" (TID:0xed7000b0, sys_thread_t:0x8da68, state:CW, thread_t: t@1, sp:0xefffe6e0 pc:0xef70aa38 threadID:0x20a00, stack_base:0xefffe918, stack_size:0x800000) prio=5
Monitor Cache Dump:
    sun.awt.motif.MToolkit@ED704C70/ED752440: owner "AWT-EventQueue-0" (0xf1d40, 1 entry)
        Waiting to acquire:
            "AWT-Motif" (0xfc6e0)
        Waiting to be notified:
            "AWT-Input" (0xfc9a0)
Registered Monitor Dump:
    Thread queue lock: <unowned>
        Waiting to be notified:
            "main" (0x8da68)
    Name and type hash table lock: <unowned>
    String intern lock: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class loading lock: <unowned>
    Java stack lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Has finalization queue lock: <unowned>
    Finalize me queue lock: <unowned>
        Waiting to be notified:
            "Finalizer thread" (0x846d0)
    Monitor registry: owner "AWT-EventQueue-0" (0xf1d40, 1 entry)

---
Note that if a canvas is used instead of the
TextArea, the JVM does _not_ crash. Also, if
using the fvwm manager there is no crash.
(Review ID: 28929)
======================================================================